Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal, and method for receiving broadcast signal

ABSTRACT

A method for transmitting and processing a broadcast signal according to an embodiment of the present invention may comprise the steps of: generating broadcast data for one or more broadcast services; generating first level signaling information comprising information describing attributes for the one or more broadcast services; generating second level signaling information comprising information for listing the one or more broadcast services; generating link layer packets comprising encoded broadcast data, the first level signaling information and the second level signaling information; and generating a broadcast signal comprising the generated link layer packets.

TECHNICAL FIELD

The present invention relates to an apparatus for transmitting a broadcast signal, an apparatus for receiving a broadcast signal and methods for transmitting and receiving a broadcast signal.

BACKGROUND ART

As analog broadcast signal transmission comes to an end, various technologies for transmitting/receiving digital broadcast signals are being developed. A digital broadcast signal may include a larger amount of video/audio data than an analog broadcast signal and further include various types of additional data in addition to the video/audio data.

DISCLOSURE Technical Problem

That is, a digital broadcast system can provide HD (high definition) images, multi channel audio and various additional services. However, data transmission efficiency for transmission of large amounts of data, robustness of transmission/reception networks and network flexibility in consideration of mobile reception equipment need to be improved for digital broadcast.

Technical Solution

The object of the present invention can be achieved by providing a method of transmitting and processing a broadcast signal, the method including generating broadcast data for one or more broadcast services, generating first level signaling information including information for describing attribute of the one or more broadcast services, generating second level signaling information including information for listing the one or more broadcast services, generating link layer packets including encoded broadcast data, the first level signaling information, and the second level signaling information, and generating a broadcast signal including the generated link layer packets, wherein the generating of the first level signaling information includes generating signaling instance included in the first level signaling information, generating signaling template for the first level signaling information, generating Diff data including data about a difference between the generated signaling instance and the generated signaling template, and generating the first level signaling information including the Diff data.

The Diff data may include signaling template identifier information for identifying signaling template to which the Diff data needs to be applied, and signaling template version information indicating a version of the signaling template identified by the signaling template identifier.

The method may further include transmitting the generated signaling template to a receiver prior to the transmitting of the Diff data to the receiver.

The method may further include processing the first level signaling information according to an asynchronous layered coding/layered coding transport (ALC/LCT) protocol to generate first level signaling LCT packets including the first level signaling information, and generating link layer packets including the generated LCT packets, wherein the LCT packets may include a transmission object identifier (TOI) field for identifying an object transmitted by the LCT packets.

The TOI field may be divided into at least three regions, a first region of the at least three regions may include fragment type information for identifying a type of signaling fragment including the signaling instance, a second region of the at least three regions may include fragment type extension information for identifying a lower type of a type of signaling fragment identified by the fragment type information, and a third region of the at least three regions may include version information indicating a version of an object identified by the fragment type information and the fragment type extension information.

The fragment type information may identify whether the signaling fragment corresponds to USBD/USD fragment, S-TSID fragment, or MPD fragment.

The fragment type information, the fragment type extension information, and the version information may be used to filter the signaling fragment by a receiver.

In another aspect of the present invention, provided herein is an apparatus for transmitting and processing a broadcast signal, the apparatus including a data encoder configured to generate broadcast data for one or more broadcast services, a first level signaling encoder configured to generate first level signaling information including information for describing attribute of the one or more broadcast services, a second level signaling encoder configured to generate second level signaling information including information for listing the one or more broadcast services, a processor configured to generate link layer packets including encoded broadcast data, the first level signaling information, and the second level signaling information, and a broadcast signal generator configured to generate a broadcast signal including the generated link layer packets, wherein the first level signaling encoder generates signaling instance included in the first level signaling information, generates signaling template for the first level signaling information, generates Diff data including data about a difference between the generated signaling instance and the generated signaling template, and generates the first level signaling information including the Diff data.

The Diff data may include signaling template identifier information for identifying signaling template to which the Diff data needs to be applied, and signaling template version information indicating a version of the signaling template identified by the signaling template identifier.

The apparatus may further include a data transmitter configured to transmit the generated signaling template to a receiver prior to the transmitting of the Diff data to the receiver.

The processor may process the first level signaling information according to an asynchronous layered coding/layered coding transport (ALC/LCT) protocol to generate first level signaling LCT packets including the first level signaling information and generates link layer packets including the generated LCT packets, and the LCT packet may include a transmission object identifier (TOI) field for identifying an object transmitted by the LCT packets.

The TOI field may be divided into at least three regions, a first region of the at least three regions may include fragment type information for identifying a type of signaling fragment including the signaling instance, a second region of the at least three regions may include fragment type extension information for identifying a lower type of a type of signaling fragment identified by the fragment type information, and a third region of the at least three regions may include version information indicating a version of an object identified by the fragment type information and the fragment type extension information.

The fragment type information may identify whether the signaling fragment corresponds to USBD/USD fragment, S-TSID fragment, or MPD fragment.

The fragment type information, the fragment type extension information, and the version information may be used to filter the signaling fragment by a receiver.

Advantageous Effects

The present invention can reduce a bandwidth for transmitting signaling and save data processing resources at a receiver.

The present invention can permit a receiver to rapidly acquire desired signaling fragment.

The present invention can control quality of service (QoS) with respect to services or service components by processing data on the basis of service characteristics, thereby providing various broadcast services.

The present invention can achieve transmission flexibility by transmitting various broadcast services through the same radio frequency (RF) signal bandwidth.

The present invention can provide methods and apparatuses for transmitting and receiving broadcast signals, which enable digital broadcast signals to be received without error even when a mobile reception device is used or even in an indoor environment.

The present invention can effectively support future broadcast services in an environment supporting future hybrid broadcasting using terrestrial broadcast networks and the Internet.

DESCRIPTION OF DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the principle of the invention. In the drawings:

FIG. 1 illustrates a receiver protocol stack according to an embodiment of the present invention;

FIG. 2 illustrates a relation between an SLT and service layer signaling (SLS) according to an embodiment of the present invention;

FIG. 3 illustrates an SLT according to an embodiment of the present invention;

FIG. 4 illustrates SLS bootstrapping and a service discovery process according to an embodiment of the present invention;

FIG. 5 illustrates a USBD fragment for ROUTE/DASH according to an embodiment of the present invention;

FIG. 6 illustrates an S-TSID fragment for ROUTE/DASH according to an embodiment of the present invention;

FIG. 7 illustrates a USBD/USD fragment for MMT according to an embodiment of the present invention;

FIG. 8 illustrates a link layer protocol architecture according to an embodiment of the present invention;

FIG. 9 illustrates a structure of a base header of a link layer packet according to an embodiment of the present invention;

FIG. 10 illustrates a structure of an additional header of a link layer packet according to an embodiment of the present invention;

FIG. 11 illustrates a structure of an additional header of a link layer packet according to another embodiment of the present invention;

FIG. 12 illustrates a header structure of a link layer packet for an MPEG-2 TS packet and an encapsulation process thereof according to an embodiment of the present invention;

FIG. 13 illustrates an example of adaptation modes in IP header compression according to an embodiment of the present invention (transmitting side);

FIG. 14 illustrates a link mapping table (LMT) and an RoHC-U description table according to an embodiment of the present invention;

FIG. 15 illustrates a structure of a link layer on a transmitter side according to an embodiment of the present invention;

FIG. 16 illustrates a structure of a link layer on a receiver side according to an embodiment of the present invention;

FIG. 17 illustrates a configuration of signaling transmission through a link layer according to an embodiment of the present invention (transmitting/receiving sides);

FIG. 18 is a block diagram illustrating a configuration of a broadcast signal transmission apparatus for future broadcast services according to an embodiment of the present invention;

FIG. 19 is a block diagram illustrating a bit interleaved coding & modulation (BICM) block according to an embodiment of the present invention;

FIG. 20 is a block diagram illustrating a bit interleaved coding & modulation (BICM) block according to another embodiment of the present invention;

FIG. 21 illustrates a bit interleaving process of physical layer signaling (PLS) according to an embodiment of the present invention;

FIG. 22 is a block diagram illustrating a configuration of a broadcast signal reception apparatus for future broadcast services according to an embodiment of the present invention;

FIG. 23 illustrates a signaling hierarchy structure of a frame according to an embodiment of the present invention;

FIG. 24 is a table illustrating PLS1 data according to an embodiment of the present invention;

FIG. 25 is a table illustrating PLS2 data according to an embodiment of the present invention;

FIG. 26 is a table illustrating PLS2 data according to another embodiment of the present invention;

FIG. 27 illustrates a logical structure of a frame according to an embodiment of the present invention;

FIG. 28 illustrates PLS mapping according to an embodiment of the present invention;

FIG. 29 illustrates time interleaving according to an embodiment of the present invention;

FIG. 30 illustrates a basic operation of a twisted row-column block interleaver according to an embodiment of the present invention;

FIG. 31 illustrates an operation of a twisted row-column block interleaver according to another embodiment of the present invention;

FIG. 32 is a block diagram illustrating an interleaving address generator including a main pseudo-random binary sequence (PRBS) generator and a sub-PRBS generator according to each FFT mode according to an embodiment of the present invention;

FIG. 33 illustrates a main PRBS used for all FFT modes according to an embodiment of the present invention;

FIG. 34 illustrates a sub-PRBS used for FFT modes and an interleaving address for frequency interleaving according to an embodiment of the present invention;

FIG. 35 illustrates a write operation of a time interleaver according to an embodiment of the present invention;

FIG. 36 is a table illustrating an interleaving type applied according to the number of PLPs;

FIG. 37 is a block diagram including a first example of a structure of a hybrid time interleaver;

FIG. 38 is a block diagram including a second example of the structure of the hybrid time interleaver;

FIG. 39 is a block diagram including a first example of a structure of a hybrid time deinterleaver;

FIG. 40 is a block diagram including a second example of the structure of the hybrid time deinterleaver;

FIG. 41 is a block diagram illustrating a hybrid broadcast reception apparatus according to an embodiment of the present invention;

FIG. 42 is a block diagram illustrating a hybrid broadcast receiver according to an embodiment of the present invention;

FIG. 43 illustrates a protocol stack of a future hybrid broadcast system according to an embodiment of the present invention;

FIG. 44 illustrates a structure of a transport frame delivered to a physical layer of a future broadcast transmission system according to an embodiment of the present invention;

FIG. 45 illustrates a transport packet of an application layer transport protocol according to an embodiment of the present invention;

FIG. 46 illustrates a method for transmitting signaling data by a future broadcast system according to an embodiment of the present invention;

FIG. 47 illustrates a syntax of a fast information table (FIT) according to an embodiment of the present invention.

FIG. 48 illustrates description about information included in the FIT according to an embodiment of the present invention.

FIG. 49 illustrates a signaling connecting structure in a procedure in which a receiver acquires a service according to an embodiment of the present invention.

FIG. 50 illustrates a syntax of an FIT according to another embodiment of the present invention.

FIG. 51 is a table showing descriptor type and locations at which descriptors can be included according to an embodiment of the present invention.

FIG. 52 illustrates a signaling_broadcast_descriptor according to an embodiment of the present invention.

FIG. 53 illustrates meaning of a signaling_on_inet_descriptor (or signaling_over_internet_descriptor) and values of inet_server_URL_type information according to an embodiment of the present invention.

FIG. 54 illustrates meaning of a capability_descriptor and values of capability_category information according to an embodiment of the present invention.

FIG. 55 illustrates a syntax of an FIT according to another embodiment of the present invention.

FIG. 56 compares methods of signaling information about service level signaling transmitted through a broadcast network according to an embodiment of the present invention.

FIG. 57 is a table showing descriptor type and locations at which descriptors can be included according to an embodiment of the present invention.

FIG. 58 illustrates an FIT in XML format according to another embodiment of the present invention.

FIG. 59 illustrates description about information included in an FIT according to an embodiment of the present invention.

FIG. 60 illustrates a signaling connecting structure in a procedure in which a receiver acquires a service according to an embodiment of the present invention.

FIG. 61 illustrates a signaling connecting structure in a procedure in which a receiver acquires a service according to another embodiment of the present invention.

FIG. 62 is a diagram showing a template delivery table of a table (or a fragment) for transmitting signaling information according to an embodiment of the present invention.

FIG. 63 is a diagram illustrating FIT and a descriptor included therein according to an embodiment of the present invention.

FIG. 64 is a diagram illustrating FIT and a descriptor included therein according to an embodiment of the present invention.

FIG. 65 is a diagram illustrating a method of operatively connecting broadcast signaling and electronic service guide (ESG) according to an embodiment of the present invention.

FIG. 66 is a diagram showing a connection relationship between ESG service fragment and signaling of the present invention, according to an embodiment of the present invention.

FIG. 67 is a view illustrating a protocol stack for a next generation broadcasting system according to an embodiment of the present invention;

FIG. 68 is a view illustrating the interface of a link layer according to an embodiment of the present invention;

FIG. 69 is a view illustrating an operation diagram of a normal mode, which is one of the operation modes of a link layer according to an embodiment of the present invention;

FIG. 70 is a view illustrating an operation diagram of a transparent mode, which is one of the operation modes of a link layer according to an embodiment of the present invention;

FIG. 71 is a view illustrating the structure of a link layer on a transmitter side according to an embodiment of the present invention (normal mode);

FIG. 72 is a view illustrating the structure of a link layer on a receiver side according to an embodiment of the present invention (normal mode);

FIG. 73 is a view illustrating the definition of a link layer based on the organization type thereof according to an embodiment of the present invention;

FIG. 74 is a view illustrating the processing of a broadcast signal, in a case in which a logical data path includes only a normal data pipe, according to an embodiment of the present invention;

FIG. 75 is a view illustrating the processing of a broadcast signal, in a case in which a logical data path includes a normal data pipe and a base data pipe, according to an embodiment of the present invention;

FIG. 76 is a view illustrating the processing of a broadcast signal, in a case in which a logical data path includes a normal data pipe and a dedicated channel, according to an embodiment of the present invention;

FIG. 77 is a view illustrating the processing of a broadcast signal, in a case in which a logical data path includes a normal data pipe, a base data pipe, and a dedicated channel, according to an embodiment of the present invention;

FIG. 78 is a view illustrating a detailed processing operation of signals and/or data in a link layer of a receiver, in a case in which a logical data path includes a normal data pipe, a base data pipe, and a dedicated channel, according to an embodiment of the present invention;

FIG. 79 is a view illustrating the syntax of a fast information channel (FIC) according to an embodiment of the present invention;

FIG. 80 is a view illustrating the syntax of an emergency alert table (EAT) according to an embodiment of the present invention;

FIG. 81 is a view illustrating a packet that is transmitted through a data pipe according to an embodiment of the present invention;

FIG. 82 is a view illustrating the detailed processing operation of signals and/or data in each protocol stack of a transmitter, in a case in which a logical data path of a physical layer includes a dedicated channel, a base DP, and a normal data DP, according to another embodiment of the present invention;

FIG. 83 is a view illustrating a detailed processing operation of signals and/or data in each protocol stack of a receiver, in a case in which a logical data path of a physical layer includes a dedicated channel, a base DP, and a normal data DP, according to another embodiment of the present invention;

FIG. 84 is a view illustrating the syntax of an FIC according to another embodiment of the present invention;

FIG. 85 is a view illustrating Signaling_Information_Part( ) according to an embodiment of the present invention;

FIG. 86 is a view illustrating a process of controlling an operation mode of a transmitter and/or a receiver in a link layer according to an embodiment of the present invention;

FIG. 87 is a view illustrating the operation in a link layer based on the value of a flag and the type of packet that is transmitted to a physical layer according to an embodiment of the present invention;

FIG. 88 is a view illustrating a descriptor for signaling a mode control parameter according to an embodiment of the present invention;

FIG. 89 is a view illustrating the operation of a transmitter that controls an operation mode according to an embodiment of the present invention;

FIG. 90 is a view illustrating the operation of a transmitter that processes a broadcast signal based on an operation mode according to an embodiment of the present invention;

FIG. 91 is a view illustrating information that identifies an encapsulation mode according to an embodiment of the present invention;

FIG. 92 is a view illustrating information that identifies a header compression mode according to an embodiment of the present invention;

FIG. 93 is a view illustrating information that identifies a packet reconfiguration mode according to an embodiment of the present invention;

FIG. 94 is a view illustrating information that identifies a context transmission mode according to an embodiment of the present invention;

FIG. 95 is a view illustrating initialization information, in a case in which RoHC is applied in a header compression mode, according to an embodiment of the present invention;

FIG. 96 is a view illustrating information that identifies a link layer signaling path configuration according to an embodiment of the present invention;

FIG. 97 is a view illustrating information about signaling path configuration in a bit mapping mode according to an embodiment of the present invention;

FIG. 98 is a flowchart illustrating a link layer initialization procedure according to an embodiment of the present invention;

FIG. 99 is a flowchart illustrating a link layer initialization procedure according to another embodiment of the present invention;

FIG. 100 is a view illustrating a signaling format in a form for transmitting an initialization parameter according to an embodiment of the present invention;

FIG. 101 is a view illustrating a signaling format in a form for transmitting an initialization parameter according to another embodiment of the present invention;

FIG. 102 is a view illustrating a signaling format in a form for transmitting an initialization parameter according to a further embodiment of the present invention;

FIG. 103 is a view illustrating a receiver according to an embodiment of the present invention;

FIG. 104 illustrates a layer structure when dedicated channels are present according to an embodiment of the present invention;

FIG. 105 illustrates a layer structure when dedicated channels are present according to another embodiment of the present invention;

FIG. 106 illustrates a layer structure when dedicated channels are independently present according to an embodiment of the present invention;

FIG. 107 illustrates a layer structure when dedicated channels are independently present according to another embodiment of the present invention;

FIG. 108 illustrates a layer structure when specific data is transmitted over a dedicated channel according to an embodiment of the present invention;

FIG. 109 illustrates a format (or dedicated format) of data transmitted over a dedicated channel according to an embodiment of the present invention;

FIG. 110 illustrates dedicated channel configuration information for signaling information about a dedicated channel according to an embodiment of the present invention;

FIG. 111 is a diagram illustrating a layered signaling structure according to an embodiment of the present invention.

FIG. 112 is a diagram illustrating a transmission path of an FIT according to an embodiment of the present invention.

FIG. 113 is a diagram for bootstrapping SLS by using FIT according to an embodiment of the present invention.

FIG. 114 is a diagram illustrating extension of 3DPP MBMS signaling for a broadcast system according to an embodiment of the present invention.

FIG. 115 is a diagram illustrating protocol stack of a broadcast system according to an embodiment of the present invention.

FIG. 116 illustrates a correlation of entities of a service management layer, a delivery layer, and a physical layer, according to an embodiment of the present invention.

FIG. 117 is a diagram illustrating a signaling structure of a broadcast system according to an embodiment of the present invention.

FIG. 118 is a diagram illustrating an FIT according to an embodiment of the present invention.

FIG. 119 is a diagram illustrating a location of a descriptor to be included in signaling for a broadcast system according to an embodiment of the present invention.

FIG. 120 is a diagram illustrating broadcast_signaling_location_descriptor( ) according to an embodiment of the present invention.

FIG. 121 is a diagram illustrating the meaning of inet_signaling_location_descriptor( ) and URL_type information according to an embodiment of the present invention.

FIG. 122 is a diagram illustrating a query term using URL_bytes information of inet_signaling_location_descriptor( ) according to an embodiment of the present invention.

FIG. 123 is a diagram illustrating capability_descriptor( ) according to an embodiment of the present invention.

FIG. 124 is a diagram illustrating FIT defined in XML according to an embodiment of the present invention.

FIG. 125 is a diagram illustrating a data model of service layer signaling for a linear service according to an embodiment of the present invention.

FIG. 126 is a diagram illustrating user service bundle description (USBD) according to an embodiment of the present invention.

FIG. 127 is a diagram illustrating an S-TSID according to an embodiment of the present invention.

FIG. 128 is a diagram illustrating ATSC_physical_layer_pipe_identifier_descriptor( ) according to an embodiment of the present invention.

FIG. 129 is a diagram illustrating a layered signaling structure of an ATSC3.0 system according to an embodiment of the present invention.

FIG. 130 is a diagram illustrating a flow of a rapid channel scan procedure according to an embodiment of the present invention.

FIG. 131 is a diagram illustrating a flow of an entire channel scan procedure according to an embodiment of the present invention.

FIG. 132 is a diagram illustrating a procedure of acquiring a service in pure broadcast according to an embodiment of the present invention.

FIG. 133 is a diagram illustrating a procedure of acquiring a service a plurality of ROUTE sessions in pure broadcast according to an embodiment of the present invention.

FIG. 134 is a diagram illustrating a procedure of bootstrapping electronic service guide (ESG) via a broadband network, according to an embodiment of the present invention.

FIG. 135 is a diagram illustrating a procedure of acquiring a service through broadcast and broadband according to an embodiment of the present invention.

FIG. 136 is a diagram illustrating signaling for an operation of changing service reception between broadcast and broadband according to an embodiment of the present invention.

FIG. 137 is a diagram illustrating signaling of receiver capability information according to an embodiment of the present invention.

FIG. 138 is a diagram illustrating the meaning of an LCT transport object identifier (TOI) for filtering signaling fragment and information included in the field according to an embodiment of the present invention.

FIG. 139 is a diagram illustrating MetadataEnvelope in the form of XML for application of template-based compression to signaling according to an embodiment of the present invention.

FIG. 140 is a diagram illustrating a compression procedure of template-based signaling fragment according to an embodiment of the present invention.

FIG. 141 is a flowchart illustrating a method of transmitting and processing a broadcast signal according to an embodiment of the present invention.

FIG. 142 is a diagram illustrating a broadcast system according to an embodiment of the present invention.

BEST MODE

Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. The detailed description, which will be given below with reference to the accompanying drawings, is intended to explain exemplary embodiments of the present invention, rather than to show the only embodiments that can be implemented according to the present invention. The following detailed description includes specific details in order to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced without such specific details.

Although the terms used in the present invention are selected from generally known and used terms, some of the terms mentioned in the description of the present invention have been selected by the applicant at his or her discretion, the detailed meanings of which are described in relevant parts of the description herein. Furthermore, it is required that the present invention is understood, not simply by the actual terms used but by the meanings of each term lying within.

The present invention provides apparatuses and methods for transmitting and receiving broadcast signals for future broadcast services. Future broadcast services according to an embodiment of the present invention include a terrestrial broadcast service, a mobile broadcast service, an ultra high definition television (UHDTV) service, etc. The present invention may process broadcast signals for the future broadcast services through non-MIMO (Multiple Input Multiple Output) or MIMO according to one embodiment. A non-MIMO scheme according to an embodiment of the present invention may include a MISO (Multiple Input Single Output) scheme, a SISO (Single Input Single Output) scheme, etc.

FIG. 1 illustrates a receiver protocol stack according to an embodiment of the present invention.

Two schemes may be used in broadcast service delivery through a broadcast network.

In a first scheme, media processing units (MPUs) are transmitted using an MMT protocol (MMTP) based on MPEG media transport (MMT). In a second scheme, dynamic adaptive streaming over HTTP (DASH) segments may be transmitted using real time object delivery over unidirectional transport (ROUTE) based on MPEG DASH.

Non-timed content including NRT media, EPG data, and other files is delivered with ROUTE. Signaling may be delivered over MMTP and/or ROUTE, while bootstrap signaling information is provided by the means of the Service List Table (SLT).

In hybrid service delivery, MPEG DASH over HTTP/TCP/IP is used on the broadband side. Media files in ISO Base Media File Format (BMFF) are used as the delivery, media encapsulation and synchronization format for both broadcast and broadband delivery. Here, hybrid service delivery may refer to a case in which one or more program elements are delivered through a broadband path.

Services are delivered using three functional layers. These are the physical layer, the delivery layer and the service management layer. The physical layer provides the mechanism by which signaling, service announcement and IP packet streams are transported over the broadcast physical layer and/or broadband physical layer. The delivery layer provides object and object flow transport functionality. It is enabled by the MMTP or the ROUTE protocol, operating on a UDP/IP multicast over the broadcast physical layer, and enabled by the HTTP protocol on a TCP/IP unicast over the broadband physical layer. The service management layer enables any type of service, such as linear TV or HTML5 application service, to be carried by the underlying delivery and physical layers.

In this figure, a protocol stack part on a broadcast side may be divided into a part transmitted through the SLT and the MMTP, and a part transmitted through ROUTE.

The SLT may be encapsulated through UDP and IP layers. Here, the SLT will be described below. The MMTP may transmit data formatted in an MPU format defined in MMT, and signaling information according to the MMTP. The data may be encapsulated through the UDP and IP layers. ROUTE may transmit data formatted in a DASH segment form, signaling information, and non-timed data such as NRT data, etc. The data may be encapsulated through the UDP and IP layers. According to a given embodiment, some or all processing according to the UDP and IP layers may be omitted. Here, the illustrated signaling information may be signaling information related to a service.

The part transmitted through the SLT and the MMTP and the part transmitted through ROUTE may be processed in the UDP and IP layers, and then encapsulated again in a data link layer. The link layer will be described below. Broadcast data processed in the link layer may be multicast as a broadcast signal through processes such as encoding/interleaving, etc. in the physical layer.

In this figure, a protocol stack part on a broadband side may be transmitted through HTTP as described above. Data formatted in a DASH segment form, signaling information, NRT information, etc. may be transmitted through HTTP. Here, the illustrated signaling information may be signaling information related to a service. The data may be processed through the TCP layer and the IP layer, and then encapsulated into the link layer. According to a given embodiment, some or all of the TCP, the IP, and the link layer may be omitted. Broadband data processed thereafter may be transmitted by unicast in the broadband through a process for transmission in the physical layer.

Service can be a collection of media components presented to the user in aggregate; components can be of multiple media types; a Service can be either continuous or intermittent; a Service can be Real Time or Non-Real Time; Real Time Service can consist of a sequence of TV programs.

FIG. 2 illustrates a relation between the SLT and SLS according to an embodiment of the present invention.

Service signaling provides service discovery and description information, and comprises two functional components: Bootstrap signaling via the Service List Table (SLT) and the Service Layer Signaling (SLS). These represent the information which is necessary to discover and acquire user services. The SLT enables the receiver to build a basic service list, and bootstrap the discovery of the SLS for each service.

The SLT can enable very rapid acquisition of basic service information. The SLS enables the receiver to discover and access services and their content components. Details of the SLT and SLS will be described below.

As described in the foregoing, the SLT may be transmitted through UDP/IP. In this instance, according to a given embodiment, data corresponding to the SLT may be delivered through the most robust scheme in this transmission.

The SLT may have access information for accessing SLS delivered by the ROUTE protocol. In other words, the SLT may be bootstrapped into SLS according to the ROUTE protocol. The SLS is signaling information positioned in an upper layer of ROUTE in the above-described protocol stack, and may be delivered through ROUTE/UDP/IP. The SLS may be transmitted through one of LCT sessions included in a ROUTE session. It is possible to access a service component corresponding to a desired service using the SLS.

In addition, the SLT may have access information for accessing an MMT signaling component delivered by MMTP. In other words, the SLT may be bootstrapped into SLS according to the MMTP. The SLS may be delivered by an MMTP signaling message defined in MMT. It is possible to access a streaming service component (MPU) corresponding to a desired service using the SLS. As described in the foregoing, in the present invention, an NRT service component is delivered through the ROUTE protocol, and the SLS according to the MMTP may include information for accessing the ROUTE protocol. In broadband delivery, the SLS is carried over HTTP(S)/TCP/IP.

FIG. 3 illustrates an SLT according to an embodiment of the present invention.

First, a description will be given of a relation among respective logical entities of service management, delivery, and a physical layer.

Services may be signaled as being one of two basic types. First type is a linear audio/video or audio-only service that may have an app-based enhancement. Second type is a service whose presentation and composition is controlled by a downloaded application that is executed upon acquisition of the service. The latter can be called an “app-based” service.

The rules regarding presence of ROUTE/LCT sessions and/or MMTP sessions for carrying the content components of a service may be as follows.

For broadcast delivery of a linear service without app-based enhancement, the service's content components can be carried by either (but not both): (1) one or more ROUTE/LCT sessions, or (2) one or more MMTP sessions.

For broadcast delivery of a linear service with app-based enhancement, the service's content components can be carried by: (1) one or more ROUTE/LCT sessions, and (2) zero or more MMTP sessions.

In certain embodiments, use of both MMTP and ROUTE for streaming media components in the same service may not be allowed.

For broadcast delivery of an app-based service, the service's content components can be carried by one or more ROUTE/LCT sessions.

Each ROUTE session comprises one or more LCT sessions which carry as a whole, or in part, the content components that make up the service. In streaming services delivery, an LCT session may carry an individual component of a user service such as an audio, video or closed caption stream. Streaming media is formatted as DASH Segments.

Each MMTP session comprises one or more MMTP packet flows which carry MMT signaling messages or as a whole, or in part, the content component. An MMTP packet flow may carry MMT signaling messages or components formatted as MPUs.

For the delivery of NRT User Services or system metadata, an LCT session carries file-based content items. These content files may consist of continuous (time-based) or discrete (non-time-based) media components of an NRT service, or metadata such as Service Signaling or ESG fragments. Delivery of system metadata such as service signaling or ESG fragments may also be achieved through the signaling message mode of MMTP.

A broadcast stream is the abstraction for an RF channel, which is defined in terms of a carrier frequency centered within a specified bandwidth. It is identified by the pair [geographic area, frequency]. A physical layer pipe (PLP) corresponds to a portion of the RF channel. Each PLP has certain modulation and coding parameters. It is identified by a PLP identifier (PLPID), which is unique within the broadcast stream it belongs to. Here, PLP can be referred to as DP (data pipe).

Each service is identified by two forms of service identifier: a compact form that is used in the SLT and is unique only within the broadcast area; and a globally unique form that is used in the SLS and the ESG. A ROUTE session is identified by a source IP address, destination IP address and destination port number. An LCT session (associated with the service component(s) it carries) is identified by a transport session identifier (TSI) which is unique within the scope of the parent ROUTE session. Properties common to the LCT sessions, and certain properties unique to individual LCT sessions, are given in a ROUTE signaling structure called a service-based transport session instance description (S-TSID), which is part of the service layer signaling. Each LCT session is carried over a single physical layer pipe. According to a given embodiment, one LCT session may be transmitted through a plurality of PLPs. Different LCT sessions of a ROUTE session may or may not be contained in different physical layer pipes. Here, the ROUTE session may be delivered through a plurality of PLPs. The properties described in the S-TSID include the TSI value and PLPID for each LCT session, descriptors for the delivery objects/files, and application layer FEC parameters.

A MMTP session is identified by destination IP address and destination port number. An MMTP packet flow (associated with the service component(s) it carries) is identified by a packet_id which is unique within the scope of the parent MMTP session. Properties common to each MMTP packet flow, and certain properties of MMTP packet flows, are given in the SLT. Properties for each MMTP session are given by MMT signaling messages, which may be carried within the MMTP session. Different MMTP packet flows of a MMTP session may or may not be contained in different physical layer pipes. Here, the MMTP session may be delivered through a plurality of PLPs. The properties described in the MMT signaling messages include the packet_id value and PLPID for each MMTP packet flow. Here, the MMT signaling messages may have a form defined in MMT, or have a deformed form according to embodiments to be described below.

Hereinafter, a description will be given of low level signaling (LLS).

Signaling information which is carried in the payload of IP packets with a well-known address/port dedicated to this function is referred to as low level signaling (LLS). The IP address and the port number may be differently configured depending on embodiments. In one embodiment, LLS can be transported in IP packets with address 224.0.23.60 and destination port 4937/udp. LLS may be positioned in a portion expressed by “SLT” on the above-described protocol stack. However, according to a given embodiment, the LLS may be transmitted through a separate physical channel (dedicated channel) in a signal frame without being subjected to processing of the UDP/IP layer.

UDP/IP packets that deliver LLS data may be formatted in a form referred to as an LLS table. A first byte of each UDP/IP packet that delivers the LLS data may correspond to a start of the LLS table. The maximum length of any LLS table is limited by the largest IP packet that can be delivered from the PHY layer, 65,507 bytes.

The LLS table may include an LLS table ID field that identifies a type of the LLS table, and an LLS table version field that identifies a version of the LLS table. According to a value indicated by the LLS table ID field, the LLS table may include the above-described SLT or a rating region table (RRT). The RRT may have information about content advisory rating.

Hereinafter, the SLT will be described. LLS can be signaling information which supports rapid channel scans and bootstrapping of service acquisition by the receiver, and SLT can be a table of signaling information which is used to build a basic service listing and provide bootstrap discovery of SLS.

The function of the SLT is similar to that of the program association table (PAT) in MPEG-2 Systems, and the fast information channel (FIC) found in ATSC Systems. For a receiver first encountering the broadcast emission, this is the place to start. SLT supports a rapid channel scan which allows a receiver to build a list of all the services it can receive, with their channel name, channel number, etc., and SLT provides bootstrap information that allows a receiver to discover the SLS for each service. For ROUTE/DASH-delivered services, the bootstrap information includes the destination IP address and destination port of the LCT session that carries the SLS. For MMT/MPU-delivered services, the bootstrap information includes the destination IP address and destination port of the MMTP session carrying the SLS.

The SLT supports rapid channel scans and service acquisition by including the following information about each service in the broadcast stream. First, the SLT can include information necessary to allow the presentation of a service list that is meaningful to viewers and that can support initial service selection via channel number or up/down selection. Second, the SLT can include information necessary to locate the service layer signaling for each service listed. That is, the SLT may include access information related to a location at which the SLS is delivered.

The illustrated SLT according to the present embodiment is expressed as an XML document having an SLT root element. According to a given embodiment, the SLT may be expressed in a binary format or an XML document.

The SLT root element of the SLT illustrated in the figure may include @bsid, @sltSectionVersion, @sltSectionNumber, @totalSltSectionNumbers, @language, @capabilities, InetSigLoc and/or Service. According to a given embodiment, the SLT root element may further include @providerId. According to a given embodiment, the SLT root element may not include @language.

The service element may include @serviceId, @SLTserviceSeqNumber, @protected, @majorChannelNo, @minorChannelNo, @serviceCategory, @shortServiceName, @hidden, @slsProtocolType, BroadcastSignaling, @slsPlpId, @slsDestinationIpAddress, @slsDestinationUdpPort, @slsSourceIpAddress, @slsMajorProtocolVersion, @SlsMinorProtocolVersion, @serviceLanguage, @broadbandAccessRequired, @capabilities and/or InetSigLoc.

According to a given embodiment, an attribute or an element of the SLT may be added/changed/deleted. Each element included in the SLT may additionally have a separate attribute or element, and some attribute or elements according to the present embodiment may be omitted. Here, a field which is marked with @ may correspond to an attribute, and a field which is not marked with @ may correspond to an element.

@bsid is an identifier of the whole broadcast stream. The value of BSID may be unique on a regional level.

@providerId can be an index of broadcaster that is using part or all of this broadcast stream. This is an optional attribute. When it's not present, it means that this broadcast stream is being used by one broadcaster. @providerId is not illustrated in the figure.

@sltSectionVersion can be a version number of the SLT section. The sltSectionVersion can be incremented by 1 when a change in the information carried within the slt occurs. When it reaches maximum value, it wraps around to 0.

@sltSectionNumber can be the number, counting from 1, of this section of the SLT. In other words, @sltSectionNumber may correspond to a section number of the SLT section. When this field is not used, @sltSectionNumber may be set to a default value of 1.

@totalSltSectionNumbers can be the total number of sections (that is, the section with the highest sltSectionNumber) of the SLT of which this section is part. sltSectionNumber and totalSltSectionNumbers together can be considered to indicate “Part M of N” of one portion of the SLT when it is sent in fragments. In other words, when the SLT is transmitted, transmission through fragmentation may be supported. When this field is not used, @totalSltSectionNumbers may be set to a default value of 1. A case in which this field is not used may correspond to a case in which the SLT is not transmitted by being fragmented.

@language can indicate primary language of the services included in this slt instance. According to a given embodiment, a value of this field may have a three-character language code defined in the ISO. This field may be omitted.

@capabilities can indicate required capabilities for decoding and meaningfully presenting the content for all the services in this slt instance.

InetSigLoc can provide a URL telling the receiver where it can acquire any requested type of data from external server(s) via broadband. This element may include @urlType as a lower field. According to a value of the @urlType field, a type of a URL provided by InetSigLoc may be indicated. According to a given embodiment, when the @urlType field has a value of 0, InetSigLoc may provide a URL of a signaling server. When the @urlType field has a value of 1, InetSigLoc may provide a URL of an ESG server. When the @urlType field has other values, the field may be reserved for future use.

The service field is an element having information about each service, and may correspond to a service entry. Service element fields corresponding to the number of services indicated by the SLT may be present. Hereinafter, a description will be given of a lower attribute/element of the service field.

@serviceId can be an integer number that uniquely identify this service within the scope of this broadcast area. According to a given embodiment, a scope of @serviceId may be changed. @SLTserviceSeqNumber can be an integer number that indicates the sequence number of the SLT service information with service ID equal to the serviceId attribute above. SLTserviceSeqNumber value can start at 0 for each service and can be incremented by 1 every time any attribute in this service element is changed. If no attribute values are changed compared to the previous Service element with a particular value of ServiceID then SLTserviceSeqNumber would not be incremented. The SLTserviceSeqNumber field wraps back to 0 after reaching the maximum value.

@protected is flag information which may indicate whether one or more components for significant reproduction of the service are in a protected state. When set to “1” (true), that one or more components necessary for meaningful presentation is protected. When set to “0” (false), this flag indicates that no components necessary for meaningful presentation of the service are protected. Default value is false.

@majorChannelNo is an integer number representing the “major” channel number of the service. An example of the field may have a range of 1 to 999.

@minorChannelNo is an integer number representing the “minor” channel number of the service. An example of the field may have a range of 1 to 999.

@serviceCategory can indicate the category of this service. This field may indicate a type that varies depending on embodiments. According to a given embodiment, when this field has values of 1, 2, and 3, the values may correspond to a linear A/V service, a linear audio only service, and an app-based service, respectively. When this field has a value of 0, the value may correspond to a service of an undefined category. When this field has other values except for 1, 2, and 3, the field may be reserved for future use. @shortServiceName can be a short string name of the Service.

@hidden can be Boolean value that when present and set to “true” indicates that the service is intended for testing or proprietary use, and is not to be selected by ordinary TV receivers. The default value is “false” when not present.

@slsProtocolType can be an attribute indicating the type of protocol of Service Layer Signaling used by this service. This field may indicate a type that varies depending on embodiments. According to a given embodiment, when this field has values of 1 and 2, protocols of SLS used by respective corresponding services may be ROUTE and MMTP, respectively. When this field has other values except for 0, the field may be reserved for future use. This field may be referred to as @slsProtocol.

BroadcastSignaling and lower attributes/elements thereof may provide information related to broadcast signaling. When the BroadcastSignaling element is not present, the child element InetSigLoc of the parent service element can be present and its attribute urlType includes URL_type 0x00 (URL to signaling server). In this case attribute url supports the query parameter svc=<service_id> where service_id corresponds to the serviceId attribute for the parent service element.

Alternatively when the BroadcastSignaling element is not present, the element InetSigLoc can be present as a child element of the slt root element and the attribute urlType of that InetSigLoc element includes URL_type 0x00 (URL to signaling server). In this case, attribute url for URL_type 0x00 supports the query parameter svc=<service_id> where service_id corresponds to the serviceId attribute for the parent Service element.

@sisPlpId can be a string representing an integer number indicating the PLP ID of the physical layer pipe carrying the SLS for this service.

@slsDestinationIpAddress can be a string containing the dotted-IPv4 destination address of the packets carrying SLS data for this service.

@slsDestinationUdpPort can be a string containing the port number of the packets carrying SLS data for this service. As described in the foregoing, SLS bootstrapping may be performed by destination IP/UDP information.

@slsSourceIpAddress can be a string containing the dotted-IPv4 source address of the packets carrying SLS data for this service.

@slsMajorProtocolVersion can be major version number of the protocol used to deliver the service layer signaling for this service. Default value is 1.

@SlsMinorProtocolVersion can be minor version number of the protocol used to deliver the service layer signaling for this service. Default value is 0.

@serviceLanguage can be a three-character language code indicating the primary language of the service. A value of this field may have a form that varies depending on embodiments.

@broadbandAccessRequired can be a Boolean indicating that broadband access is required for a receiver to make a meaningful presentation of the service. Default value is false. When this field has a value of True, the receiver needs to access a broadband for significant service reproduction, which may correspond to a case of hybrid service delivery.

@capabilities can represent required capabilities for decoding and meaningfully presenting the content for the service with service ID equal to the serviceId attribute above.

InetSigLoc can provide a URL for access to signaling or announcement information via broadband, if available. Its datatype can be an extension of the anyURL datatype, adding an @urlType attribute that indicates what the URL gives access to. An @urlType field of this field may indicate the same meaning as that of the @urlType field of InetSigLoc described above. When an InetSigLoc element of attribute URL_type 0x00 is present as an element of the SLT, it can be used to make HTTP requests for signaling metadata. The HTTP POST message body may include a service term. When the InetSigLoc element appears at the section level, the service term is used to indicate the service to which the requested signaling metadata objects apply. If the service term is not present, then the signaling metadata objects for all services in the section are requested. When the InetSigLoc appears at the service level, then no service term is needed to designate the desired service. When an InetSigLoc element of attribute URL_type 0x01 is provided, it can be used to retrieve ESG data via broadband. If the element appears as a child element of the service element, then the URL can be used to retrieve ESG data for that service. If the element appears as a child element of the SLT element, then the URL can be used to retrieve ESG data for all services in that section.

In another example of the SLT, @sltSectionVersion, @sltSectionNumber, @totalSltSectionNumbers and/or @language fields of the SLT may be omitted

In addition, the above-described InetSigLoc field may be replaced by @sltInetSigUri and/or @sltInetEsgUri field. The two fields may include the URI of the signaling server and URI information of the ESG server, respectively. The InetSigLoc field corresponding to a lower field of the SLT and the InetSigLoc field corresponding to a lower field of the service field may be replaced in a similar manner.

The suggested default values may vary depending on embodiments. An illustrated “use” column relates to the respective fields. Here, “1” may indicate that a corresponding field is an essential field, and “0 . . . 1” may indicate that a corresponding field is an optional field.

FIG. 4 illustrates SLS bootstrapping and a service discovery process according to an embodiment of the present invention.

Hereinafter, SLS will be described.

SLS can be signaling which provides information for discovery and acquisition of services and their content components.

For ROUTE/DASH, the SLS for each service describes characteristics of the service, such as a list of its components and where to acquire them, and the receiver capabilities required to make a meaningful presentation of the service. In the ROUTE/DASH system, the SLS includes the user service bundle description (USBD), the S-TSID and the DASH media presentation description (MPD). Here, USBD or user service description (USD) is one of SLS XML fragments, and may function as a signaling herb that describes specific descriptive information. USBD/USD may be extended beyond 3GPP MBMS. Details of USBD/USD will be described below.

The service signaling focuses on basic attributes of the service itself, especially those attributes needed to acquire the service. Properties of the service and programming that are intended for viewers appear as service announcement, or ESG data.

Having separate Service Signaling for each service permits a receiver to acquire the appropriate SLS for a service of interest without the need to parse the entire SLS carried within a broadcast stream.

For optional broadband delivery of Service Signaling, the SLT can include HTTP URLs where the Service Signaling files can be obtained, as described above.

LLS is used for bootstrapping SLS acquisition, and subsequently, the SLS is used to acquire service components delivered on either ROUTE sessions or MMTP sessions. The described figure illustrates the following signaling sequences. Receiver starts acquiring the SLT described above. Each service identified by service_id delivered over ROUTE sessions provides SLS bootstrapping information: PLPID(#1), source IP address (sIP1), destination IP address (dIP1), and destination port number (dPort1). Each service identified by service_id delivered over MMTP sessions provides SLS bootstrapping information: PLPID(#2), destination IP address (dIP2), and destination port number (dPort2).

For streaming services delivery using ROUTE, the receiver can acquire SLS fragments carried over the IP/UDP/LCT session and PLP; whereas for streaming services delivery using MMTP, the receiver can acquire SLS fragments carried over an MMTP session and PLP. For service delivery using ROUTE, these SLS fragments include USBD/USD fragments, S-TSID fragments, and MPD fragments. They are relevant to one service. USBD/USD fragments describe service layer properties and provide URI references to S-TSID fragments and URI references to MPD fragments. In other words, the USBD/USD may refer to S-TSID and MPD. For service delivery using MMTP, the USBD references the MMT signaling's MPT message, the MP Table of which provides identification of package ID and location information for assets belonging to the service. Here, an asset is a multimedia data entity, and may refer to a data entity which is combined into one unique ID and is used to generate one multimedia presentation. The asset may correspond to a service component included in one service. The MPT message is a message having the MP table of MMT. Here, the MP table may be an MMT package table having information about content and an MMT asset. Details may be similar to a definition in MMT. Here, media presentation may correspond to a collection of data that establishes bounded/unbounded presentation of media content.

The S-TSID fragment provides component acquisition information associated with one service and mapping between DASH Representations found in the MPD and in the TSI corresponding to the component of the service. The S-TSID can provide component acquisition information in the form of a TSI and the associated DASH representation identifier, and PLPID carrying DASH segments associated with the DASH representation. By the PLPID and TSI values, the receiver collects the audio/video components from the service and begins buffering DASH media segments then applies the appropriate decoding processes.

For USBD listing service components delivered on MMTP sessions, as illustrated by “Service #2” in the described figure, the receiver also acquires an MPT message with matching MMT_package_id to complete the SLS. An MPT message provides the full list of service components comprising a service and the acquisition information for each component. Component acquisition information includes MMTP session information, the PLPID carrying the session and the packet_id within that session.

According to a given embodiment, for example, in ROUTE, two or more S-TSID fragments may be used. Each fragment may provide access information related to LCT sessions delivering content of each service.

In ROUTE, S-TSID, USBD/USD, MPD, or an LCT session delivering S-TSID, USBD/USD or MPD may be referred to as a service signaling channel. In MMTP, USBD/UD, an MMT signaling message, or a packet flow delivering the MMTP or USBD/UD may be referred to as a service signaling channel.

Unlike the illustrated example, one ROUTE or MMTP session may be delivered through a plurality of PLPs. In other words, one service may be delivered through one or more PLPs. As described in the foregoing, one LCT session may be delivered through one PLP. Unlike the figure, according to a given embodiment, components included in one service may be delivered through different ROUTE sessions. In addition, according to a given embodiment, components included in one service may be delivered through different MMTP sessions. According to a given embodiment, components included in one service may be delivered separately through a ROUTE session and an MMTP session. Although not illustrated, components included in one service may be delivered via broadband (hybrid delivery).

FIG. 5 illustrates a USBD fragment for ROUTE/DASH according to an embodiment of the present invention.

Hereinafter, a description will be given of SLS in delivery based on ROUTE.

SLS provides detailed technical information to the receiver to enable the discovery and access of services and their content components. It can include a set of XML-encoded metadata fragments carried over a dedicated LCT session. That LCT session can be acquired using the bootstrap information contained in the SLT as described above. The SLS is defined on a per-service level, and it describes the characteristics and access information of the service, such as a list of its content components and how to acquire them, and the receiver capabilities required to make a meaningful presentation of the service. In the ROUTE/DASH system, for linear services delivery, the SLS consists of the following metadata fragments: USBD, S-TSID and the DASH MPD. The SLS fragments can be delivered on a dedicated LCT transport session with TSI=0. According to a given embodiment, a TSI of a particular LCT session (dedicated LCT session) in which an SLS fragment is delivered may have a different value. According to a given embodiment, an LCT session in which an SLS fragment is delivered may be signaled using the SLT or another scheme.

ROUTE/DASH SLS can include the user service bundle description (USBD) and service-based transport session instance description (S-TSID) metadata fragments. These service signaling fragments are applicable to both linear and application-based services. The USBD fragment contains service identification, device capabilities information, references to other SLS fragments required to access the service and constituent media components, and metadata to enable the receiver to determine the transport mode (broadcast and/or broadband) of service components. The S-TSID fragment, referenced by the USBD, provides transport session descriptions for the one or more ROUTE/LCT sessions in which the media content components of a service are delivered, and descriptions of the delivery objects carried in those LCT sessions. The USBD and S-TSID will be described below.

In streaming content signaling in ROUTE-based delivery, a streaming content signaling component of SLS corresponds to an MPD fragment. The MPD is typically associated with linear services for the delivery of DASH Segments as streaming content. The MPD provides the resource identifiers for individual media components of the linear/streaming service in the form of Segment URLs, and the context of the identified resources within the Media Presentation. Details of the MPD will be described below.

In app-based enhancement signaling in ROUTE-based delivery, app-based enhancement signaling pertains to the delivery of app-based enhancement components, such as an application logic file, locally-cached media files, network content items, or a notification stream. An application can also retrieve locally-cached data over a broadband connection when available.

Hereinafter, a description will be given of details of USBD/USD illustrated in the figure.

The top level or entry point SLS fragment is the USBD fragment. An illustrated USBD fragment is an example of the present invention, basic fields of the USBD fragment not illustrated in the figure may be additionally provided according to a given embodiment. As described in the foregoing, the illustrated USBD fragment has an extended form, and may have fields added to a basic configuration.

The illustrated USBD may have a bundleDescription root element. The bundleDescription root element may have a userServiceDescription element. The userServiceDescription element may correspond to an instance for one service.

The userServiceDescription element may include @serviceId, @atsc:serviceId, @atsc:serviceStatus, @atsc:fullMPDUri, @atsc:sTSIDUri, name, serviceLanguage, atsc:capabilityCode and/or deliveryMethod.

@serviceId can be a globally unique URI that identifies a service, unique within the scope of the BSID. This parameter can be used to link to ESG data(Service @globalServiceID).

@atsc:serviceId is a reference to corresponding service entry in LLS(SLT). The value of this attribute is the same value of serviceId assigned to the entry.

@atsc:serviceStatus can specify the status of this service. The value indicates whether this service is active or inactive. When set to “1” (true), that indicates service is active. When this field is not used, @atsc:serviceStatus may be set to a default value of 1.

@atsc:fullMPDUri can reference an MPD fragment which contains descriptions for contents components of the service delivered over broadcast and optionally, also over broadband.

@atsc:sTSIDUri can reference the S-TSID fragment which provides access related parameters to the Transport sessions carrying contents of this service.

name can indicate name of the service as given by the lang attribute. name element can include lang attribute, which indicating language of the service name. The language can be specified according to XML datatypes.

serviceLanguage can represent available languages of the service. The language can be specified according to XML datatypes.

atsc:capabilityCode can specify the capabilities required in the receiver to be able to create a meaningful presentation of the content of this service. According to a given embodiment, this field may specify a predefined capability group. Here, the capability group may be a group of capability attribute values for significant presentation. This field may be omitted according to a given embodiment.

deliveryMethod can be a container of transport related information pertaining to the contents of the service over broadcast and (optionally) broadband modes of access. Referring to data included in the service, when the number of the data is N, delivery schemes for respective data may be described by this element. The deliveryMethod may include an r12:broadcastAppService element and an r12:unicastAppService element. Each lower element may include a basePattern element as a lower element.

r12:broadcastAppService can be a DASH Representation delivered over broadcast, in multiplexed or non-multiplexed form, containing the corresponding media component(s) belonging to the service, across all Periods of the affiliated media presentation. In other words, each of the fields may indicate DASH representation delivered through the broadcast network.

r12:unicastAppService can be a DASH Representation delivered over broadband, in multiplexed or non-multiplexed form, containing the constituent media content component(s) belonging to the service, across all periods of the affiliated media presentation. In other words, each of the fields may indicate DASH representation delivered via broadband.

basePattern can be a character pattern for use by the receiver to match against any portion of the segment URL used by the DASH client to request media segments of a parent representation under its containing period. A match implies that the corresponding requested media segment is carried over broadcast transport. In a URL address for receiving DASH representation expressed by each of the r12:broadcastAppService element and the r12:unicastAppService element, a part of the URL, etc. may have a particular pattern. The pattern may be described by this field. Some data may be distinguished using this information. The proposed default values may vary depending on embodiments. The “use” column illustrated in the figure relates to each field. Here, M may denote an essential field, O may denote an optional field, OD may denote an optional field having a default value, and CM may denote a conditional essential field. 0 . . . 1 to 0 . . . N may indicate the number of available fields.

FIG. 6 illustrates an S-TSID fragment for ROUTE/DASH according to an embodiment of the present invention.

Hereinafter, a description will be given of the S-TSID illustrated in the figure in detail.

S-TSID can be an SLS XML fragment which provides the overall session description information for transport session(s) which carry the content components of a service. The S-TSID is the SLS metadata fragment that contains the overall transport session description information for the zero or more ROUTE sessions and constituent LCT sessions in which the media content components of a service are delivered. The S-TSID also includes file metadata for the delivery object or object flow carried in the LCT sessions of the service, as well as additional information on the payload formats and content components carried in those LCT sessions.

Each instance of the S-TSID fragment is referenced in the USBD fragment by the @atsc:sTSIDUri attribute of the userServiceDescription element. The illustrated S-TSID according to the present embodiment is expressed as an XML document. According to a given embodiment, the S-TSID may be expressed in a binary format or as an XML document.

The illustrated S-TSID may have an S-TSID root element. The S-TSID root element may include @serviceId and/or RS.

@serviceID can be a reference corresponding service element in the USD. The value of this attribute can reference a service with a corresponding value of service_id.

The RS element may have information about a ROUTE session for delivering the service data. Service data or service components may be delivered through a plurality of ROUTE sessions, and thus the number of RS elements may be 1 to N.

The RS element may include @bsid, @sIpAddr, @dIpAddr, @dport, @PLPID and/or LS.

@bsid can be an identifier of the broadcast stream within which the content component(s) of the broadcastAppService are carried. When this attribute is absent, the default broadcast stream is the one whose PLPs carry SLS fragments for this service. Its value can be identical to that of the broadcast_stream_id in the SLT.

@sIpAddr can indicate source IP address. Here, the source IP address may be a source IP address of a ROUTE session for delivering a service component included in the service. As described in the foregoing, service components of one service may be delivered through a plurality of ROUTE sessions. Thus, the service components may be transmitted using another ROUTE session other than the ROUTE session for delivering the S-TSID. Therefore, this field may be used to indicate the source IP address of the ROUTE session. A default value of this field may be a source IP address of a current ROUTE session. When a service component is delivered through another ROUTE session, and thus the ROUTE session needs to be indicated, a value of this field may be a value of a source IP address of the ROUTE session. In this case, this field may correspond to M, that is, an essential field.

@dIpAddr can indicate destination IP address. Here, a destination IP address may be a destination IP address of a ROUTE session that delivers a service component included in a service. For a similar case to the above description of @sIpAddr, this field may indicate a destination IP address of a ROUTE session that delivers a service component. A default value of this field may be a destination IP address of a current ROUTE session. When a service component is delivered through another ROUTE session, and thus the ROUTE session needs to be indicated, a value of this field may be a value of a destination IP address of the ROUTE session. In this case, this field may correspond to M, that is, an essential field.

@dport can indicate destination port. Here, a destination port may be a destination port of a ROUTE session that delivers a service component included in a service. For a similar case to the above description of @sIpAddr, this field may indicate a destination port of a ROUTE session that delivers a service component. A default value of this field may be a destination port number of a current ROUTE session. When a service component is delivered through another ROUTE session, and thus the ROUTE session needs to be indicated, a value of this field may be a destination port number value of the ROUTE session. In this case, this field may correspond to M, that is, an essential field.

@PLPID may be an ID of a PLP for a ROUTE session expressed by an RS. A default value may be an ID of a PLP of an LCT session including a current S-TSID. According to a given embodiment, this field may have an ID value of a PLP for an LCT session for delivering an S-TSID in the ROUTE session, and may have ID values of all PLPs for the ROUTE session.

An LS element may have information about an LCT session for delivering a service data. Service data or service components may be delivered through a plurality of LCT sessions, and thus the number of LS elements may be 1 to N.

The LS element may include @tsi, @PLPID, @bw, @startTime, @endTime, SrcFlow and/or RprFlow.

@tsi may indicate a TSI value of an LCT session for delivering a service component of a service.

@PLPID may have ID information of a PLP for the LCT session. This value may be overwritten on a basic ROUTE session value.

@bw may indicate a maximum bandwidth value. @startTime may indicate a start time of the LCT session. @endTime may indicate an end time of the LCT session. A SrcFlow element may describe a source flow of ROUTE. An RprFlow element may describe a repair flow of ROUTE.

The proposed default values may be varied according to an embodiment. The “use” column illustrated in the figure relates to each field. Here, M may denote an essential field, O may denote an optional field, OD may denote an optional field having a default value, and CM may denote a conditional essential field. 0 . . . 1 to 0 . . . N may indicate the number of available fields.

Hereinafter, a description will be given of MPD for ROUTE/DASH.

The MPD is an SLS metadata fragment which contains a formalized description of a DASH Media Presentation, corresponding to a linear service of a given duration defined by the broadcaster (for example a single TV program, or the set of contiguous linear TV programs over a period of time). The contents of the MPD provide the resource identifiers for Segments and the context for the identified resources within the Media Presentation. The data structure and semantics of the MPD fragment can be according to the MPD defined by MPEG DASH.

One or more of the DASH Representations conveyed in the MPD can be carried over broadcast. The MPD may describe additional Representations delivered over broadband, e.g. in the case of a hybrid service, or to support service continuity in handoff from broadcast to broadcast due to broadcast signal degradation (e.g. driving through a tunnel).

FIG. 7 illustrates a USBD/USD fragment for MMT according to an embodiment of the present invention.

MMT SLS for linear services comprises the USBD fragment and the MMT Package (MP) table. The MP table is as described above. The USBD fragment contains service identification, device capabilities information, references to other SLS information required to access the service and constituent media components, and the metadata to enable the receiver to determine the transport mode (broadcast and/or broadband) of the service components. The MP table for MPU components, referenced by the USBD, provides transport session descriptions for the MMTP sessions in which the media content components of a service are delivered and the descriptions of the Assets carried in those MMTP sessions.

The streaming content signaling component of the SLS for MPU components corresponds to the MP table defined in MMT. The MP table provides a list of MMT assets where each asset corresponds to a single service component and the description of the location information for this component.

USBD fragments may also contain references to the S-TSID and the MPD as described above, for service components delivered by the ROUTE protocol and the broadband, respectively. According to a given embodiment, in delivery through MMT, a service component delivered through the ROUTE protocol is NRT data, etc. Thus, in this case, MPD may be unnecessary. In addition, in delivery through MMT, information about an LCT session for delivering a service component, which is delivered via broadband, is unnecessary, and thus an S-TSID may be unnecessary. Here, an MMT package may be a logical collection of media data delivered using MMT. Here, an MMTP packet may refer to a formatted unit of media data delivered using MMT. An MPU may refer to a generic container of independently decodable timed/non-timed data. Here, data in the MPU is media codec agnostic.

Hereinafter, a description will be given of details of the USBD/USD illustrated in the figure.

The illustrated USBD fragment is an example of the present invention, and basic fields of the USBD fragment may be additionally provided according to an embodiment. As described in the foregoing, the illustrated USBD fragment has an extended form, and may have fields added to a basic structure.

The illustrated USBD according to an embodiment of the present invention is expressed as an XML document. According to a given embodiment, the USBD may be expressed in a binary format or as an XML document.

The illustrated USBD may have a bundleDescription root element. The bundleDescription root element may have a userServiceDescription element. The userServiceDescription element may be an instance for one service.

The userServiceDescription element may include @serviceId, @atsc:serviceId, name, serviceLanguage, atsc:capabilityCode, atsc:Channel, atsc:mpuComponent, atsc:routeComponent, atsc:broadbandComponent and/or atsc:ComponentInfo.

Here, @serviceId, @atsc:serviceId, name, serviceLanguage, and atsc:capabilityCode may be as described above. The lang field below the name field may be as described above. atsc:capabilityCode may be omitted according to a given embodiment.

The userServiceDescription element may further include an atsc:contentAdvisoryRating element according to an embodiment. This element may be an optional element. atsc:contentAdvisoryRating can specify the content advisory rating. This field is not illustrated in the figure.

atsc:Channel may have information about a channel of a service. The atsc:Channel element may include @atsc:majorChannelNo, @atsc:minorChannelNo, @atsc:serviceLang, @atsc:serviceGenre, @atsc:serviceIcon and/or atsc:ServiceDescription. @atsc:majorChannelNo, @atsc:minorChannelNo, and @atsc:serviceLang may be omitted according to a given embodiment.

@atsc:majorChannelNo is an attribute that indicates the major channel number of the service.

@atsc:minorChannelNo is an attribute that indicates the minor channel number of the service.

@atsc:serviceLang is an attribute that indicates the primary language used in the service.

@atsc:serviceGenre is an attribute that indicates primary genre of the service.

@atsc:serviceIcon is an attribute that indicates the Uniform Resource Locator (URL) for the icon used to represent this service.

atsc:ServiceDescription includes service description, possibly in multiple languages. atsc:ServiceDescription includes can include @atsc:serviceDescrText and/or @atsc:serviceDescrLang.

@atsc:serviceDescrText is an attribute that indicates description of the service.

@atsc:serviceDescrLang is an attribute that indicates the language of the serviceDescrText attribute above.

atsc:mpuComponent may have information about a content component of a service delivered in a form of an MPU. atsc:mpuComponent may include @atsc:mmtPackageId and/or @atsc:nextMmtPackageId.

@atsc:mmtPackageId can reference a MMT Package for content components of the service delivered as MPUs.

@atsc:nextMmtPackageId can reference a MMT Package to be used after the one referenced by @atsc:mmtPackageId in time for content components of the service delivered as MPUs.

atsc:routeComponent may have information about a content component of a service delivered through ROUTE. atsc:routeComponent may include @atsc:sTSIDUri, @sTSIDPlpId, @sTSIDDestinationIpAddress, @sTSIDDestinationUdpPort, @sTSIDSourceIpAddress, @sTSIDMajorProtocolVersion and/or @sTSIDMinorProtocolVersion.

@atsc:sTSIDUri can be a reference to the S-TSID fragment which provides access related parameters to the Transport sessions carrying contents of this service. This field may be the same as a URI for referring to an S-TSID in USBD for ROUTE described above. As described in the foregoing, in service delivery by the MMTP, service components, which are delivered through NRT, etc., may be delivered by ROUTE. This field may be used to refer to the S-TSID therefor.

@sTSIDPlpId can be a string representing an integer number indicating the PLP ID of the physical layer pipe carrying the S-TSID for this service. (default: current physical layer pipe).

@sTSIDDestinationIpAddress can be a string containing the dotted-IPv4 destination address of the packets carrying S-TSID for this service. (default: current MMTP session's source IP address)

@sTSIDDestinationUdpPort can be a string containing the port number of the packets carrying S-TSID for this service.

@sTSIDSourceIpAddress can be a string containing the dotted-IPv4 source address of the packets carrying S-TSID for this service.

@sTSIDMajorProtocolVersion can indicate major version number of the protocol used to deliver the S-TSID for this service. Default value is 1.

@sTSIDMinorProtocolVersion can indicate minor version number of the protocol used to deliver the S-TSID for this service. Default value is 0.

atsc:broadbandComponent may have information about a content component of a service delivered via broadband. In other words, atsc:broadbandComponent may be a field on the assumption of hybrid delivery. atsc:broadbandComponent may further include @atsc:fullfMPDUri.

@atsc:fullfMPDUri can be a reference to an MPD fragment which contains descriptions for contents components of the service delivered over broadband.

An atsc:ComponentInfo field may have information about an available component of a service. The atsc:ComponentInfo field may have information about a type, a role, a name, etc. of each component. The number of atsc:ComponentInfo fields may correspond to the number (N) of respective components. The atsc:ComponentInfo field may include @atsc:componentType, @atsc:componentRole, @atsc:componentProtectedFlag, @atsc:componentId and/or @atsc:componentName.

@atsc:componentType is an attribute that indicates the type of this component. Value of 0 indicates an audio component. Value of 1 indicates a video component. Value of 2 indicated a closed caption component. Value of 3 indicates an application component. Values 4 to 7 are reserved. A meaning of a value of this field may be differently set depending on embodiments.

@atsc:componentRole is an attribute that indicates the role or kind of this component.

For audio (when componentType attribute above is equal to 0): values of componentRole attribute are as follows: 0=Complete main, 1=Music and Effects, 2=Dialog, 3=Commentary, 4=Visually Impaired, 5=Hearing Impaired, 6=Voice-Over, 7-254=reserved, 255=unknown.

For video (when componentType attribute above is equal to 1) values of componentRole attribute are as follows: 0=Primary video, 1=Alternative camera view, 2=Other alternative video component, 3=Sign language inset, 4=Follow subject video, 5=3D video left view, 6=3D video right view, 7=3D video depth information, 8=Part of video array <x,y> of <n,m>, 9=Follow-Subject metadata, 10-254=reserved, 255=unknown.

For Closed Caption component (when componentType attribute above is equal to 2) values of componentRole attribute are as follows: 0=Normal, 1=Easy reader, 2-254=reserved, 255=unknown.

When componentType attribute above is between 3 to 7, inclusive, the componentRole can be equal to 255. A meaning of a value of this field may be differently set depending on embodiments.

@atsc:componentProtectedFlag is an attribute that indicates if this component is protected (e.g. encrypted). When this flag is set to a value of 1 this component is protected (e.g. encrypted). When this flag is set to a value of 0 this component is not protected (e.g. encrypted). When not present the value of componentProtectedFlag attribute is inferred to be equal to 0. A meaning of a value of this field may be differently set depending on embodiments.

@atsc:componentId is an attribute that indicates the identifier of this component. The value of this attribute can be the same as the asset_id in the MP table corresponding to this component.

@atsc:componentName is an attribute that indicates the human readable name of this component.

The proposed default values may vary depending on embodiments. The “use” column illustrated in the figure relates to each field. Here, M may denote an essential field, O may denote an optional field, OD may denote an optional field having a default value, and CM may denote a conditional essential field. 0 . . . 1 to 0 . . . N may indicate the number of available fields.

Hereinafter, a description will be given of MPD for MMT.

The Media Presentation Description is an SLS metadata fragment corresponding to a linear service of a given duration defined by the broadcaster (for example a single TV program, or the set of contiguous linear TV programs over a period of time). The contents of the MPD provide the resource identifiers for segments and the context for the identified resources within the media presentation. The data structure and semantics of the MPD can be according to the MPD defined by MPEG DASH.

In the present embodiment, an MPD delivered by an MMTP session describes Representations delivered over broadband, e.g. in the case of a hybrid service, or to support service continuity in handoff from broadcast to broadband due to broadcast signal degradation (e.g. driving under a mountain or through a tunnel).

Hereinafter, a description will be given of an MMT signaling message for MMT.

When MMTP sessions are used to carry a streaming service, MMT signaling messages defined by MMT are delivered by MMTP packets according to signaling message mode defined by MMT. The value of the packet_id field of MMTP packets carrying service layer signaling is set to ‘00’ except for MMTP packets carrying MMT signaling messages specific to an asset, which can be set to the same packet_id value as the MMTP packets carrying the asset. Identifiers referencing the appropriate package for each service are signaled by the USBD fragment as described above. MMT Package Table (MPT) messages with matching MMT_package_id can be delivered on the MMTP session signaled in the SLT. Each MMTP session carries MMT signaling messages specific to its session or each asset delivered by the MMTP session.

In other words, it is possible to access USBD of the MMTP session by specifying an IP destination address/port number, etc. of a packet having the SLS for a particular service in the SLT. As described in the foregoing, a packet ID of an MMTP packet carrying the SLS may be designated as a particular value such as 00, etc. It is possible to access an MPT message having a matched packet ID using the above-described package IP information of USBD. As described below, the MPT message may be used to access each service component/asset.

The following MMTP messages can be delivered by the MMTP session signaled in the SLT.

MMT Package Table (MPT) message: This message carries an MP (MMT Package) table which contains the list of all Assets and their location information as defined by MMT. If an Asset is delivered by a PLP different from the current PLP delivering the MP table, the identifier of the PLP carrying the asset can be provided in the MP table using physical layer pipe identifier descriptor. The physical layer pipe identifier descriptor will be described below.

MMT ATSC3 (MA3) message mmt_atsc3_message( ): This message carries system metadata specific for services including service layer signaling as described above. mmt_atsc3_message( ) will be described below.

The following MMTP messages can be delivered by the MMTP session signaled in the SLT, if required.

Media Presentation Information (MPI) message: This message carries an MPI table which contains the whole document or a subset of a document of presentation information. An MP table associated with the MPI table also can be delivered by this message.

Clock Relation Information (CRI) message: This message carries a CRI table which contains clock related information for the mapping between the NTP timestamp and the MPEG-2 STC. According to a given embodiment, the CRI message may not be delivered through the MMTP session.

The following MMTP messages can be delivered by each MMTP session carrying streaming content.

Hypothetical Receiver Buffer Model message: This message carries information required by the receiver to manage its buffer.

Hypothetical Receiver Buffer Model Removal message: This message carries information required by the receiver to manage its MMT de-capsulation buffer.

Hereinafter, a description will be given of mmt_atsc3_message( ) corresponding to one of MMT signaling messages. An MMT Signaling message mmt_atsc3_message( ) is defined to deliver information specific to services according to the present invention described above. The signaling message may include message ID, version, and/or length fields corresponding to basic fields of the MMT signaling message. A payload of the signaling message may include service ID information, content type information, content version information, content compression information and/or URI information. The content type information may indicate a type of data included in the payload of the signaling message. The content version information may indicate a version of data included in the payload, and the content compression information may indicate a type of compression applied to the data. The URI information may have URI information related to content delivered by the message.

Hereinafter, a description will be given of the physical layer pipe identifier descriptor.

The physical layer pipe identifier descriptor is a descriptor that can be used as one of descriptors of the MP table described above. The physical layer pipe identifier descriptor provides information about the PLP carrying an asset. If an asset is delivered by a PLP different from the current PLP delivering the MP table, the physical layer pipe identifier descriptor can be used as an asset descriptor in the associated MP table to identify the PLP carrying the asset. The physical layer pipe identifier descriptor may further include BSID information in addition to PLP ID information. The BSID may be an ID of a broadcast stream that delivers an MMTP packet for an asset described by the descriptor.

FIG. 8 illustrates a link layer protocol architecture according to an embodiment of the present invention.

Hereinafter, a link layer will be described.

The link layer is the layer between the physical layer and the network layer, and transports the data from the network layer to the physical layer at the sending side and transports the data from the physical layer to the network layer at the receiving side. The purpose of the link layer includes abstracting all input packet types into a single format for processing by the physical layer, ensuring flexibility and future extensibility for as yet undefined input types. In addition, processing within the link layer ensures that the input data can be transmitted in an efficient manner, for example by providing options to compress redundant information in the headers of input packets. The operations of encapsulation, compression and so on are referred to as the link layer protocol and packets created using this protocol are called link layer packets. The link layer may perform functions such as packet encapsulation, overhead reduction and/or signaling transmission, etc.

Hereinafter, packet encapsulation will be described. Link layer protocol allows encapsulation of any type of packet, including ones such as IP packets and MPEG-2 TS. Using link layer protocol, the physical layer need only process one single packet format, independent of the network layer protocol type (here we consider MPEG-2 TS packet as a kind of network layer packet.) Each network layer packet or input packet is transformed into the payload of a generic link layer packet. Additionally, concatenation and segmentation can be performed in order to use the physical layer resources efficiently when the input packet sizes are particularly small or large.

As described in the foregoing, segmentation may be used in packet encapsulation. When the network layer packet is too large to process easily in the physical layer, the network layer packet is divided into two or more segments. The link layer packet header includes protocol fields to perform segmentation on the sending side and reassembly on the receiving side. When the network layer packet is segmented, each segment can be encapsulated to link layer packet in the same order as original position in the network layer packet. Also each link layer packet which includes a segment of network layer packet can be transported to PHY layer consequently.

As described in the foregoing, concatenation may be used in packet encapsulation. When the network layer packet is small enough for the payload of a link layer packet to include several network layer packets, the link layer packet header includes protocol fields to perform concatenation. The concatenation is combining of multiple small sized network layer packets into one payload. When the network layer packets are concatenated, each network layer packet can be concatenated to payload of link layer packet in the same order as original input order. Also each packet which constructs a payload of link layer packet can be whole packet, not a segment of packet.

Hereinafter, overhead reduction will be described. Use of the link layer protocol can result in significant reduction in overhead for transport of data on the physical layer. The link layer protocol according to the present invention may provide IP overhead reduction and/or MPEG-2 TS overhead reduction. In IP overhead reduction, IP packets have a fixed header format, however some of the information which is needed in a communication environment may be redundant in a broadcast environment. Link layer protocol provides mechanisms to reduce the broadcast overhead by compressing headers of IP packets. In MPEG-2 TS overhead reduction, link layer protocol provides sync byte removal, null packet deletion and/or common header removal (compression). First, sync byte removal provides an overhead reduction of one byte per TS packet, secondly a null packet deletion mechanism removes the 188 byte null TS packets in a manner that they can be re-inserted at the receiver and finally a common header removal mechanism.

For signaling transmission, in the link layer protocol, a particular format for the signaling packet may be provided for link layer signaling, which will be described below.

In the illustrated link layer protocol architecture according to an embodiment of the present invention, link layer protocol takes as input network layer packets such as IPv4, MPEG-2 TS and so on as input packets. Future extension indicates other packet types and protocol which is also possible to be input in link layer. Link layer protocol also specifies the format and signaling for any link layer signaling, including information about mapping to specific channel to the physical layer. Figure also shows how ALP incorporates mechanisms to improve the efficiency of transmission, via various header compression and deletion algorithms. In addition, the link layer protocol may basically encapsulate input packets.

FIG. 9 illustrates a structure of a base header of a link layer packet according to an embodiment of the present invention. Hereinafter, the structure of the header will be described.

A link layer packet can include a header followed by the data payload. The header of a link layer packet can include a base header, and may include an additional header depending on the control fields of the base header. The presence of an optional header is indicated from flag fields of the additional header. According to a given embodiment, a field indicating the presence of an additional header and an optional header may be positioned in the base header.

Hereinafter, the structure of the base header will be described. The base header for link layer packet encapsulation has a hierarchical structure. The base header can be two bytes in length and is the minimum length of the link layer packet header.

The illustrated base header according to the present embodiment may include a Packet_Type field, a PC field and/or a length field. According to a given embodiment, the base header may further include an HM field or an S/C field.

Packet_Type field can be a 3-bit field that indicates the original protocol or packet type of the input data before encapsulation into a link layer packet. An IPv4 packet, a compressed IP packet, a link layer signaling packet, and other types of packets may have the base header structure and may be encapsulated. However, according to a given embodiment, the MPEG-2 TS packet may have a different particular structure, and may be encapsulated. When the value of Packet_Type is “000”, “001” “100” or “111”, that is the original data type of an ALP packet is one of an IPv4 packet, a compressed IP packet, link layer signaling or extension packet. When the MPEG-2 TS packet is encapsulated, the value of Packet_Type can be “010”. Other values of the Packet_Type field may be reserved for future use.

Payload_Configuration (PC) field can be a 1-bit field that indicates the configuration of the payload. A value of 0 can indicate that the link layer packet carries a single, whole input packet and the following field is the Header_Mode field. A value of 1 can indicate that the link layer packet carries more than one input packet (concatenation) or a part of a large input packet (segmentation) and the following field is the Segmentation_Concatenation field.

Header_Mode (HM) field can be a 1-bit field, when set to 0, that can indicate there is no additional header, and that the length of the payload of the link layer packet is less than 2048 bytes. This value may be varied depending on embodiments. A value of 1 can indicate that an additional header for single packet defined below is present following the Length field. In this case, the length of the payload is larger than 2047 bytes and/or optional features can be used (substream identification, header extension, etc.). This value may be varied depending on embodiments. This field can be present only when Payload_Configuration field of the link layer packet has a value of 0.

Segmentation_Concatenation (S/C) field can be a 1-bit field, when set to 0, that can indicate that the payload carries a segment of an input packet and an additional header for segmentation defined below is present following the Length field. A value of 1 can indicate that the payload carries more than one complete input packet and an additional header for concatenation defined below is present following the Length field. This field can be present only when the value of Payload_Configuration field of the ALP packet is 1.

Length field can be an 11-bit field that indicates the 11 least significant bits (LSBs) of the length in bytes of payload carried by the link layer packet. When there is a Length_MSB field in the following additional header, the length field is concatenated with the Length_MSB field, and is the LSB to provide the actual total length of the payload. The number of bits of the length field may be changed to another value rather than 11 bits.

Following types of packet configuration are thus possible: a single packet without any additional header, a single packet with an additional header, a segmented packet and a concatenated packet. According to a given embodiment, more packet configurations may be made through a combination of each additional header, an optional header, an additional header for signaling information to be described below, and an additional header for time extension.

FIG. 10 illustrates a structure of an additional header of a link layer packet according to an embodiment of the present invention.

Various types of additional headers may be present. Hereinafter, a description will be given of an additional header for a single packet.

This additional header for single packet can be present when Header_Mode (HM)=“1”. The Header_Mode (HM) can be set to 1 when the length of the payload of the link layer packet is larger than 2047 bytes or when the optional fields are used. The additional header for single packet is shown in Figure (tsib10010).

Length_MSB field can be a 5-bit field that can indicate the most significant bits (MSBs) of the total payload length in bytes in the current link layer packet, and is concatenated with the Length field containing the 11 least significant bits (LSBs) to obtain the total payload length. The maximum length of the payload that can be signaled is therefore 65535 bytes. The number of bits of the length field may be changed to another value rather than 11 bits. In addition, the number of bits of the Length_MSB field may be changed, and thus a maximum expressible payload length may be changed. According to a given embodiment, each length field may indicate a length of a whole link layer packet rather than a payload.

SIF (Substream Identifier Flag) field can be a 1-bit field that can indicate whether the substream ID (SID) is present after the HEF field or not. When there is no SID in this link layer packet, SIF field can be set to 0. When there is a SID after HEF field in the link layer packet, SIF can be set to 1. The detail of SID is described below.

HEF (Header Extension Flag) field can be a 1-bit field that can indicate, when set to 1, presence of an additional header for future extension. A value of 0 can indicate that this extension header is not present.

Hereinafter, a description will be given of an additional header when segmentation is used.

This additional header (tsib10020) can be present when Segmentation_Concatenation (S/C)=“0”. Segment_Sequence_Number can be a 5-bit unsigned integer that can indicate the order of the corresponding segment carried by the link layer packet. For the link layer packet which carries the first segment of an input packet, the value of this field can be set to 0x0. This field can be incremented by one with each additional segment belonging to the segmented input packet.

Last_Segment_Indicator (LSI) can be a 1-bit field that can indicate, when set to 1, that the segment in this payload is the last one of input packet. A value of 0, can indicate that it is not last segment.

SIF (Substream Identifier Flag) can be a 1-bit field that can indicate whether the SID is present after the HEF field or not. When there is no SID in the link layer packet, SIF field can be set to 0. When there is a SID after the HEF field in the link layer packet, SIF can be set to 1.

HEF (Header Extension Flag) can be a This 1-bit field that can indicate, when set to 1, that the optional header extension is present after the additional header for future extensions of the link layer header. A value of 0 can indicate that optional header extension is not present.

According to a given embodiment, a packet ID field may be additionally provided to indicate that each segment is generated from the same input packet. This field may be unnecessary and thus be omitted when segments are transmitted in order.

Hereinafter, a description will be given of an additional header when concatenation is used.

This additional header (tsib10030) can be present when Segmentation_Concatenation (S/C)=“1”.

Length_MSB can be a 4-bit field that can indicate MSB bits of the payload length in bytes in this link layer packet. The maximum length of the payload is 32767 bytes for concatenation. As described in the foregoing, a specific numeric value may be changed.

Count can be a field that can indicate the number of the packets included in the link layer packet. The number of the packets included in the link layer packet, 2 can be set to this field. So, its maximum value of concatenated packets in a link layer packet is 9. A scheme in which the count field indicates the number may be varied depending on embodiments. That is, the numbers from 1 to 8 may be indicated.

HEF (Header Extension Flag) can be a 1-bit field that can indicate, when set to 1 the optional header extension is present after the additional header for future extensions of the link layer header. A value of 0, can indicate extension header is not present.

Component_Length can be a 12-bit length field that can indicate the length in byte of each packet. Component_Length fields are included in the same order as the packets present in the payload except last component packet. The number of length field can be indicated by (Count+1). According to a given embodiment, length fields, the number of which is the same as a value of the count field, may be present. When a link layer header consists of an odd number of Component_Length, four stuffing bits can follow after the last Component_Length field. These bits can be set to 0. According to a given embodiment, a Component_length field indicating a length of a last concatenated input packet may not be present. In this case, the length of the last concatenated input packet may correspond to a length obtained by subtracting a sum of values indicated by respective Component_length fields from a whole payload length.

Hereinafter, the optional header will be described.

As described in the foregoing, the optional header may be added to a rear of the additional header. The optional header field can contain SID and/or header extension. The SID is used to filter out specific packet stream in the link layer level. One example of SID is the role of service identifier in a link layer stream carrying multiple services. The mapping information between a service and the SID value corresponding to the service can be provided in the SLT, if applicable. The header extension contains extended field for future use. Receivers can ignore any header extensions which they do not understand.

SID (Substream Identifier) can be a 8-bit field that can indicate the sub stream identifier for the link layer packet. If there is optional header extension, SID present between additional header and optional header extension.

Header_Extension ( ) can include the fields defined below.

Extension_Type can be an 8-bit field that can indicate the type of the Header_Extension ( ).

Extension_Length can be an 8-bit field that can indicate the length of the Header Extension ( ) in bytes counting from the next byte to the last byte of the Header_Extension ( ).

Extension_Byte can be a byte representing the value of the Header_Extension ( ).

FIG. 11 illustrates a structure of an additional header of a link layer packet according to another embodiment of the present invention.

Hereinafter, a description will be given of an additional header for signaling information.

How link layer signaling is incorporated into link layer packets are as follows. Signaling packets are identified by when the Packet_Type field of the base header is equal to 100.

Figure (tsib11010) shows the structure of the link layer packets containing additional header for signaling information. In addition to the link layer header, the link layer packet can consist of two additional parts, additional header for signaling information and the actual signaling data itself. The total length of the link layer signaling packet is shown in the link layer packet header.

The additional header for signaling information can include following fields. According to a given embodiment, some fields may be omitted.

Signaling_Type can be an 8-bit field that can indicate the type of signaling.

Signaling_Type_Extension can be a 16-bit filed that can indicate the attribute of the signaling. Detail of this field can be defined in signaling specification.

Signaling_Version can be an 8-bit field that can indicate the version of signaling.

Signaling_Format can be a 2-bit field that can indicate the data format of the signaling data. Here, a signaling format may refer to a data format such as a binary format, an XML format, etc.

Signaling_Encoding can be a 2-bit field that can specify the encoding/compression format. This field may indicate whether compression is not performed and which type of compression is performed.

Hereinafter, a description will be given of an additional header for packet type extension.

In order to provide a mechanism to allow an almost unlimited number of additional protocol and packet types to be carried by link layer in the future, the additional header is defined. Packet type extension can be used when Packet_type is 111 in the base header as described above. Figure (tsib11020) shows the structure of the link layer packets containing additional header for type extension.

The additional header for type extension can include following fields. According to a given embodiment, some fields may be omitted.

extended_type can be a 16-bit field that can indicate the protocol or packet type of the input encapsulated in the link layer packet as payload. This field cannot be used for any protocol or packet type already defined by Packet_Type field.

FIG. 12 illustrates a header structure of a link layer packet for an MPEG-2 TS packet and an encapsulation process thereof according to an embodiment of the present invention.

Hereinafter, a description will be given of a format of the link layer packet when the MPEG-2 TS packet is input as an input packet.

In this case, the Packet_Type field of the base header is equal to 010. Multiple TS packets can be encapsulated within each link layer packet. The number of TS packets is signaled via the NUMTS field. In this case, as described in the foregoing, a particular link layer packet header format may be used.

Link layer provides overhead reduction mechanisms for MPEG-2 TS to enhance the transmission efficiency. The sync byte (0x47) of each TS packet can be deleted. The option to delete NULL packets and similar TS headers is also provided.

In order to avoid unnecessary transmission overhead, TS null packets (PID=0x1FFF) may be removed. Deleted null packets can be recovered in receiver side using DNP field. The DNP field indicates the count of deleted null packets. Null packet deletion mechanism using DNP field is described below.

In order to achieve more transmission efficiency, similar header of MPEG-2 TS packets can be removed. When two or more successive TS packets have sequentially increased continuity counter fields and other header fields are the same, the header is sent once at the first packet and the other headers are deleted. HDM field can indicate whether the header deletion is performed or not. Detailed procedure of common TS header deletion is described below.

When all three overhead reduction mechanisms are performed, overhead reduction can be performed in sequence of sync removal, null packet deletion, and common header deletion. According to a given embodiment, a performance order of respective mechanisms may be changed. In addition, some mechanisms may be omitted according to a given embodiment.

The overall structure of the link layer packet header when using MPEG-2 TS packet encapsulation is depicted in Figure (tsib12010).

Hereinafter, a description will be given of each illustrated field. Packet Type can be a 3-bit field that can indicate the protocol type of input packet as describe above. For MPEG-2 TS packet encapsulation, this field can always be set to 010.

NUMTS (Number of TS packets) can be a 4-bit field that can indicate the number of TS packets in the payload of this link layer packet. A maximum of 16 TS packets can be supported in one link layer packet. The value of NUMTS=0 can indicate that 16 TS packets are carried by the payload of the link layer packet. For all other values of NUMTS, the same number of TS packets are recognized, e.g. NUMTS=0001 means one TS packet is carried.

AHF (Additional Header Flag) can be a field that can indicate whether the additional header is present of not. A value of 0 indicates that there is no additional header. A value of 1 indicates that an additional header of length 1-byte is present following the base header. If null TS packets are deleted or TS header compression is applied this field can be set to 1. The additional header for TS packet encapsulation consists of the following two fields and is present only when the value of AHF in this link layer packet is set to 1.

HDM (Header Deletion Mode) can be a 1-bit field that indicates whether TS header deletion can be applied to this link layer packet. A value of 1 indicates that TS header deletion can be applied. A value of “0” indicates that the TS header deletion method is not applied to this link layer packet.

DNP (Deleted Null Packets) can be a 7-bit field that indicates the number of deleted null TS packets prior to this link layer packet. A maximum of 128 null TS packets can be deleted. When HDM=0 the value of DNP=0 can indicate that 128 null packets are deleted. When HDM=1 the value of DNP=0 can indicate that no null packets are deleted. For all other values of DNP, the same number of null packets are recognized, e.g. DNP=5 means 5 null packets are deleted.

The number of bits of each field described above may be changed. According to the changed number of bits, a minimum/maximum value of a value indicated by the field may be changed. These numbers may be changed by a designer.

Hereinafter, SYNC byte removal will be described.

When encapsulating TS packets into the payload of a link layer packet, the SYNC byte (0x47) from the start of each TS packet can be deleted. Hence the length of the MPEG2-TS packet encapsulated in the payload of the link layer packet is always of length 187 bytes (instead of 188 bytes originally).

Hereinafter, null packet deletion will be described.

Transport Stream rules require that bit rates at the output of a transmitter's multiplexer and at the input of the receiver's de-multiplexer are constant in time and the end-to-end delay is also constant. For some Transport Stream input signals, null packets may be present in order to accommodate variable bitrate services in a constant bitrate stream. In this case, in order to avoid unnecessary transmission overhead, TS null packets (that is TS packets with PID=0x1FFF) may be removed. The process is carried-out in a way that the removed null packets can be re-inserted in the receiver in the exact place where they were originally, thus guaranteeing constant bitrate and avoiding the need for PCR time stamp updating.

Before generation of a link layer packet, a counter called DNP (Deleted Null-Packets) can first be reset to zero and then incremented for each deleted null packet preceding the first non-null TS packet to be encapsulated into the payload of the current link layer packet. Then a group of consecutive useful TS packets is encapsulated into the payload of the current link layer packet and the value of each field in its header can be determined. After the generated link layer packet is injected to the physical layer, the DNP is reset to zero. When DNP reaches its maximum allowed value, if the next packet is also a null packet, this null packet is kept as a useful packet and encapsulated into the payload of the next link layer packet. Each link layer packet can contain at least one useful TS packet in its payload.

Hereinafter, TS packet header deletion will be described. TS packet header deletion may be referred to as TS packet header compression.

When two or more successive TS packets have sequentially increased continuity counter fields and other header fields are the same, the header is sent once at the first packet and the other headers are deleted. When the duplicated MPEG-2 TS packets are included in two or more successive TS packets, header deletion cannot be applied in transmitter side. HDM field can indicate whether the header deletion is performed or not. When TS header deletion is performed, HDM can be set to 1. In the receiver side, using the first packet header, the deleted packet headers are recovered, and the continuity counter is restored by increasing it in order from that of the first header.

An example tsib12020 illustrated in the figure is an example of a process in which an input stream of a TS packet is encapsulated into a link layer packet. First, a TS stream including TS packets having SYNC byte (0x47) may be input. First, sync bytes may be deleted through a sync byte deletion process. In this example, it is presumed that null packet deletion is not performed.

Here, it is presumed that packet headers of eight TS packets have the same field values except for CC, that is, a continuity counter field value. In this case, TS packet deletion/compression may be performed. Seven remaining TS packet headers are deleted except for a first TS packet header corresponding to CC=1. The processed TS packets may be encapsulated into a payload of the link layer packet.

In a completed link layer packet, a Packet_Type field corresponds to a case in which TS packets are input, and thus may have a value of 010. A NUMTS field may indicate the number of encapsulated TS packets. An AHF field may be set to 1 to indicate the presence of an additional header since packet header deletion is performed. An HDM field may be set to 1 since header deletion is performed. DNP may be set to 0 since null packet deletion is not performed.

FIG. 13 illustrates an example of adaptation modes in IP header compression according to an embodiment of the present invention (transmitting side).

Hereinafter, IP header compression will be described.

In the link layer, IP header compression/decompression scheme can be provided. IP header compression can include two parts: header compressor/decompressor and adaptation module. The header compression scheme can be based on the Robust Header Compression (RoHC). In addition, for broadcasting usage, adaptation function is added.

In the transmitter side, ROHC compressor reduces the size of header for each packet. Then, adaptation module extracts context information and builds signaling information from each packet stream. In the receiver side, adaptation module parses the signaling information associated with the received packet stream and attaches context information to the received packet stream. ROHC decompressor reconstructs the original IP packet by recovering the packet header.

The header compression scheme can be based on the RoHC as described above. In particular, in the present system, an RoHC framework can operate in a unidirctional mode (U mode) of the RoHC. In addition, in the present system, it is possible to use an RoHC UDP header compression profile which is identified by a profile identifier of 0x0002.

Hereinafter, adaptation will be described.

In case of transmission through the unidirectional link, if a receiver has no information of context, decompressor cannot recover the received packet header until receiving full context. This may cause channel change delay and turn on delay. For this reason, context information and configuration parameters between compressor and decompressor can be always sent with packet flow.

The Adaptation function provides out-of-band transmission of the configuration parameters and context information. Out-of-band transmission can be done through the link layer signaling. Therefore, the adaptation function is used to reduce the channel change delay and decompression error due to loss of context information.

Hereinafter, extraction of context information will be described.

Context information may be extracted using various schemes according to adaptation mode. In the present invention, three examples will be described below. The scope of the present invention is not restricted to the examples of the adaptation mode to be described below. Here, the adaptation mode may be referred to as a context extraction mode.

Adaptation Mode 1 (not illustrated) may be a mode in which no additional operation is applied to a basic RoHC packet stream. In other words, the adaptation module may operate as a buffer in this mode. Therefore, in this mode, context information may not be included in link layer signaling

In Adaptation Mode 2 (tsib13010), the adaptation module can detect the IR packet from ROHC packet flow and extract the context information (static chain). After extracting the context information, each IR packet can be converted to an IR-DYN packet. The converted IR-DYN packet can be included and transmitted inside the ROHC packet flow in the same order as IR packet, replacing the original packet.

In Adaptation Mode 3 (tsib13020), the adaptation module can detect the IR and IR-DYN packet from ROHC packet flow and extract the context information. The static chain and dynamic chain can be extracted from IR packet and dynamic chain can be extracted from IR-DYN packet. After extracting the context information, each IR and IR-DYN packet can be converted to a compressed packet. The compressed packet format can be the same with the next packet of IR or IR-DYN packet. The converted compressed packet can be included and transmitted inside the ROHC packet flow in the same order as IR or IR-DYN packet, replacing the original packet.

Signaling (context) information can be encapsulated based on transmission structure. For example, context information can be encapsulated to the link layer signaling. In this case, the packet type value can be set to “100”.

In the above-described Adaptation Modes 2 and 3, a link layer packet for context information may have a packet type field value of 100. In addition, a link layer packet for compressed IP packets may have a packet type field value of 001. The values indicate that each of the signaling information and the compressed IP packets are included in the link layer packet as described above.

Hereinafter, a description will be given of a method of transmitting the extracted context information.

The extracted context information can be transmitted separately from ROHC packet flow, with signaling data through specific physical data path. The transmission of context depends on the configuration of the physical layer path. The context information can be sent with other link layer signaling through the signaling data pipe.

In other words, the link layer packet having the context information may be transmitted through a signaling PLP together with link layer packets having other link layer signaling information (Packet_Type=100). Compressed IP packets from which context information is extracted may be transmitted through a general PLP (Packet_Type=001). Here, depending on embodiments, the signaling PLP may refer to an L1 signaling path. In addition, depending on embodiments, the signaling PLP may not be separated from the general PLP, and may refer to a particular and general PLP through which the signaling information is transmitted.

At a receiving side, prior to reception of a packet stream, a receiver may need to acquire signaling information. When receiver decodes initial PLP to acquire the signaling information, the context signaling can be also received. After the signaling acquisition is done, the PLP to receive packet stream can be selected. In other words, the receiver may acquire the signaling information including the context information by selecting the initial PLP. Here, the initial PLP may be the above-described signaling PLP. Thereafter, the receiver may select a PLP for acquiring a packet stream. In this way, the context information may be acquired prior to reception of the packet stream.

After the PLP for acquiring the packet stream is selected, the adaptation module can detect IR-DYN packet form received packet flow. Then, the adaptation module parses the static chain from the context information in the signaling data. This is similar to receiving the IR packet. For the same context identifier, IR-DYN packet can be recovered to IR packet. Recovered ROHC packet flow can be sent to ROHC decompressor. Thereafter, decompression may be started.

FIG. 14 illustrates a link mapping table (LMT) and an RoHC-U description table according to an embodiment of the present invention.

Hereinafter, link layer signaling will be described.

Generally, link layer signaling is operates under IP level. At the receiver side, link layer signaling can be obtained earlier than IP level signaling such as Service List Table (SLT) and Service Layer Signaling (SLS). Therefore, link layer signaling can be obtained before session establishment.

For link layer signaling, there can be two kinds of signaling according input path: internal link layer signaling and external link layer signaling. The internal link layer signaling is generated in link layer at transmitter side. And the link layer takes the signaling from external module or protocol. This kind of signaling information is considered as external link layer signaling. If some signaling need to be obtained prior to IP level signaling, external signaling is transmitted in format of link layer packet.

The link layer signaling can be encapsulated into link layer packet as described above. The link layer packets can carry any format of link layer signaling, including binary and XML. The same signaling information may not be transmitted in different formats for the link layer signaling.

Internal link layer signaling may include signaling information for link mapping. The Link Mapping Table (LMT) provides a list of upper layer sessions carried in a PLP. The LMT also provides addition information for processing the link layer packets carrying the upper layer sessions in the link layer.

An example of the LMT (tsib14010) according to the present invention is illustrated.

signaling_type can be an 8-bit unsigned integer field that indicates the type of signaling carried by this table. The value of signaling_type field for Link Mapping Table (LMT) can be set to 0x01.

PLP_ID can be an 8-bit field that indicates the PLP corresponding to this table.

num_session can be an 8-bit unsigned integer field that provides the number of upper layer sessions carried in the PLP identified by the above PLP_ID field. When the value of signaling_type field is 0x01, this field can indicate the number of UDP/IP sessions in the PLP.

src_IP_add can be a 32-bit unsigned integer field that contains the source IP address of an upper layer session carried in the PLP identified by the PLP_ID field.

dst_IP_add can be a 32-bit unsigned integer field that contains the destination IP address of an upper layer session carried in the PLP identified by the PLP_ID field.

src_UDP_port can be a 16-bit unsigned integer field that represents the source UDP port number of an upper layer session carried in the PLP identified by the PLP_ID field.

dst_UDP_port can be a 16-bit unsigned integer field that represents the destination UDP port number of an upper layer session carried in the PLP identified by the PLP ID field.

SID_flag can be a 1-bit Boolean field that indicates whether the link layer packet carrying the upper layer session identified by above 4 fields, Src_IP_add, Dst_IP_add, Src_UDP_Port and Dst_UDP_Port, has an SID field in its optional header. When the value of this field is set to 0, the link layer packet carrying the upper layer session may not have an SID field in its optional header. When the value of this field is set to 1, the link layer packet carrying the upper layer session can have an SID field in its optional header and the value the SID field can be same as the following SID field in this table.

compressed_flag can be a 1-bit Boolean field that indicates whether the header compression is applied the link layer packets carrying the upper layer session identified by above 4 fields, Src_IP_add, Dst_IP_add, Src_UDP_Port and Dst_UDP_Port. When the value of this field is set to 0, the link layer packet carrying the upper layer session may have a value of 0x00 of Packet_Type field in its base header. When the value of this field is set to 1, the link layer packet carrying the upper layer session may have a value of 0x01 of Packet_Type field in its base header and the Context_ID field can be present.

SID can be an 8-bit unsigned integer field that indicates substream identifier for the link layer packets carrying the upper layer session identified by above 4 fields, Src_IP_add, Dst_IP_add, Src_UDP_Port and Dst_UDP_Port. This field can be present when the value of SID_flag is equal to 1.

context_id can be an 8-bit field that provides a reference for the context id (CID) provided in the ROHC-U description table. This field can be present when the value of compressed_flag is equal to 1.

An example of the RoHC-U description table (tsib14020) according to the present invention is illustrated. As described in the foregoing, the RoHC-U adaptation module may generate information related to header compression.

signaling_type can be an 8-bit field that indicates the type of signaling carried by this table. The value of signaling_type field for ROHC-U description table (RDT) can be set to “0x02”.

PLP_ID can be an 8-bit field that indicates the PLP corresponding to this table.

context_id can be an 8-bit field that indicates the context id (CID) of the compressed IP stream. In this system, 8-bit CID can be used for large CID.

context_profile can be an 8-bit field that indicates the range of protocols used to compress the stream. This field can be omitted.

adaptation_mode can be a 2-bit field that indicates the mode of adaptation module in this PLP. Adaptation modes have been described above.

context_config can be a 2-bit field that indicates the combination of the context information. If there is no context information in this table, this field may be set to “0x0”. If the static_chain( ) or dynamic_chain( ) byte is included in this table, this field may be set to “0x01” or “0x02” respectively. If both of the static_chain( ) and dynamic_chain( ) byte are included in this table, this field may be set to “0x03”.

context_length can be an 8-bit field that indicates the length of the static chain byte sequence. This field can be omitted.

static_chain_byte ( ) can be a field that conveys the static information used to initialize the ROHC-U decompressor. The size and structure of this field depend on the context profile.

dynamic_chain_byte ( ) can be a field that conveys the dynamic information used to initialize the ROHC-U decompressor. The size and structure of this field depend on the context profile.

The static_chain_byte can be defined as sub-header information of IR packet. The dynamic_chain_byte can be defined as sub-header information of IR packet and IR-DYN packet.

FIG. 15 illustrates a structure of a link layer on a transmitter side according to an embodiment of the present invention.

The present embodiment presumes that an IP packet is processed. From a functional point of view, the link layer on the transmitter side may broadly include a link layer signaling part in which signaling information is processed, an overhead reduction part, and/or an encapsulation part. In addition, the link layer on the transmitter side may include a scheduler for controlling and scheduling an overall operation of the link layer and/or input and output parts of the link layer.

First, signaling information of an upper layer and/or a system parameter tsib15010 may be delivered to the link layer. In addition, an IP stream including IP packets may be delivered to the link layer from an IP layer tsib15110.

As described above, the scheduler tsib15020 may determine and control operations of several modules included in the link layer. The delivered signaling information and/or system parameter tsib15010 may be filterer or used by the scheduler tsib15020. Information, which corresponds to a part of the delivered signaling information and/or system parameter tsib15010, necessary for a receiver may be delivered to the link layer signaling part. In addition, information, which corresponds to a part of the signaling information, necessary for an operation of the link layer may be delivered to an overhead reduction controller tsib15120 or an encapsulation controller tsib15180.

The link layer signaling part may collect information to be transmitted as a signal in a physical layer, and convert/configure the information in a form suitable for transmission. The link layer signaling part may include a signaling manager tsib15030, a signaling formatter tsib15040, and/or a buffer for channels tsib15050.

The signaling manager tsib15030 may receive signaling information delivered from the scheduler tsib15020 and/or signaling (and/or context) information delivered from the overhead reduction part. The signaling manager tsib15030 may determine a path for transmission of the signaling information for delivered data. The signaling information may be delivered through the path determined by the signaling manager tsib15030. As described in the foregoing, signaling information to be transmitted through a divided channel such as the FIC, the EAS, etc. may be delivered to the signaling formatter tsib15040, and other signaling information may be delivered to an encapsulation buffer tsib15070.

The signaling formatter tsib15040 may format related signaling information in a form suitable for each divided channel such that signaling information may be transmitted through a separately divided channel. As described in the foregoing, the physical layer may include separate physically/logically divided channels. The divided channels may be used to transmit FIC signaling information or EAS-related information. The FIC or EAS-related information may be sorted by the signaling manager tsib15030, and input to the signaling formatter tsib15040. The signaling formatter tsib15040 may format the information based on each separate channel. When the physical layer is designed to transmit particular signaling information through a separately divided channel other than the FIC and the EAS, a signaling formatter for the particular signaling information may be additionally provided. Through this scheme, the link layer may be compatible with various physical layers.

The buffer for channels tsib15050 may deliver the signaling information received from the signaling formatter tsib15040 to separate dedicated channels tsib15060. The number and content of the separate channels may vary depending on embodiments.

As described in the foregoing, the signaling manager tsib15030 may deliver signaling information, which is not delivered to a particular channel, to the encapsulation buffer tsib15070. The encapsulation buffer tsib15070 may function as a buffer that receives the signaling information which is not delivered to the particular channel.

An encapsulation block for signaling information tsib15080 may encapsulate the signaling information which is not delivered to the particular channel. A transmission buffer tsib15090 may function as a buffer that delivers the encapsulated signaling information to a DP for signaling information tsib15100. Here, the DP for signaling information tsib15100 may refer to the above-described PLS region.

The overhead reduction part may allow efficient transmission by removing overhead of packets delivered to the link layer. It is possible to configure overhead reduction parts corresponding to the number of IP streams input to the link layer.

An overhead reduction buffer tsib15130 may receive an IP packet delivered from an upper layer. The received IP packet may be input to the overhead reduction part through the overhead reduction buffer tsib15130.

An overhead reduction controller tsib15120 may determine whether to perform overhead reduction on a packet stream input to the overhead reduction buffer tsib15130. The overhead reduction controller tsib15120 may determine whether to perform overhead reduction for each packet stream. When overhead reduction is performed on a packet stream, packets may be delivered to a robust header compression (RoHC) compressor tsib15140 to perform overhead reduction. When overhead reduction is not performed on a packet stream, packets may be delivered to the encapsulation part to perform encapsulation without overhead reduction. Whether to perform overhead reduction of packets may be determined based on the signaling information tsib15010 delivered to the link layer. The signaling information may be delivered to the encapsulation controller tsib15180 by the scheduler tsib15020.

The RoHC compressor tsib15140 may perform overhead reduction on a packet stream. The RoHC compressor tsib15140 may perform an operation of compressing a header of a packet. Various schemes may be used for overhead reduction. Overhead reduction may be performed using a scheme proposed by the present invention. The present invention presumes an IP stream, and thus an expression “RoHC compressor” is used. However, the name may be changed depending on embodiments. The operation is not restricted to compression of the IP stream, and overhead reduction of all types of packets may be performed by the RoHC compressor tsib15140.

A packet stream configuration block tsib15150 may separate information to be transmitted to a signaling region and information to be transmitted to a packet stream from IP packets having compressed headers. The information to be transmitted to the packet stream may refer to information to be transmitted to a DP region. The information to be transmitted to the signaling region may be delivered to a signaling and/or context controller tsib15160. The information to be transmitted to the packet stream may be transmitted to the encapsulation part.

The signaling and/or context controller tsib15160 may collect signaling and/or context information and deliver the signaling and/or context information to the signaling manager in order to transmit the signaling and/or context information to the signaling region.

The encapsulation part may perform an operation of encapsulating packets in a form suitable for a delivery to the physical layer. It is possible to configure encapsulation parts corresponding to the number of IP streams.

An encapsulation buffer tsib15170 may receive a packet stream for encapsulation. Packets subjected to overhead reduction may be received when overhead reduction is performed, and an input IP packet may be received without change when overhead reduction is not performed.

An encapsulation controller tsib15180 may determine whether to encapsulate an input packet stream. When encapsulation is performed, the packet stream may be delivered to a segmentation/concatenation block tsib15190. When encapsulation is not performed, the packet stream may be delivered to a transmission buffer tsib15230. Whether to encapsulate packets may be determined based on the signaling information tsib15010 delivered to the link layer. The signaling information may be delivered to the encapsulation controller tsib15180 by the scheduler tsib15020.

In the segmentation/concatenation block tsib15190, the above-described segmentation or concatenation operation may be performed on packets. In other words, when an input IP packet is longer than a link layer packet corresponding to an output of the link layer, one IP packet may be segmented into several segments to configure a plurality of link layer packet payloads. On the other hand, when an input IP packet is shorter than a link layer packet corresponding to an output of the link layer, several IP packets may be concatenated to configure one link layer packet payload.

A packet configuration table tsib15200 may have configuration information of a segmented and/or concatenated link layer packet. A transmitter and a receiver may have the same information in the packet configuration table tsib15200. The transmitter and the receiver may refer to the information of the packet configuration table tsib15200. An index value of the information of the packet configuration table tsib15200 may be included in a header of the link layer packet.

A link layer header information block tsib15210 may collect header information generated in an encapsulation process. In addition, the link layer header information block tsib15210 may collect header information included in the packet configuration table tsib15200. The link layer header information block tsib15210 may configure header information according to a header structure of the link layer packet.

A header attachment block tsib15220 may add a header to a payload of a segmented and/or concatenated link layer packet. The transmission buffer tsib15230 may function as a buffer to deliver the link layer packet to a DP tsib15240 of the physical layer.

The respective blocks, modules, or parts may be configured as one module/protocol or a plurality of modules/protocols in the link layer.

FIG. 16 illustrates a structure of a link layer on a receiver side according to an embodiment of the present invention.

The present embodiment presumes that an IP packet is processed. From a functional point of view, the link layer on the receiver side may broadly include a link layer signaling part in which signaling information is processed, an overhead processing part, and/or a decapsulation part. In addition, the link layer on the receiver side may include a scheduler for controlling and scheduling overall operation of the link layer and/or input and output parts of the link layer.

First, information received through a physical layer may be delivered to the link layer. The link layer may process the information, restore an original state before being processed at a transmitter side, and then deliver the information to an upper layer. In the present embodiment, the upper layer may be an IP layer.

Information, which is separated in the physical layer and delivered through a particular channel tsib16030, may be delivered to a link layer signaling part. The link layer signaling part may determine signaling information received from the physical layer, and deliver the determined signaling information to each part of the link layer.

A buffer for channels tsib16040 may function as a buffer that receives signaling information transmitted through particular channels. As described in the foregoing, when physically/logically divided separate channels are present in the physical layer, it is possible to receive signaling information transmitted through the channels. When the information received from the separate channels is segmented, the segmented information may be stored until complete information is configured.

A signaling decoder/parser tsib16050 may verify a format of the signaling information received through the particular channel, and extract information to be used in the link layer. When the signaling information received through the particular channel is encoded, decoding may be performed. In addition, according to a given embodiment, it is possible to verify integrity, etc. of the signaling information.

A signaling manager tsib16060 may integrate signaling information received through several paths. Signaling information received through a DP for signaling tsib16070 to be described below may be integrated in the signaling manager tsib16060. The signaling manager tsib16060 may deliver signaling information necessary for each part in the link layer. For example, the signaling manager tsib16060 may deliver context information, etc. for recovery of a packet to the overhead processing part. In addition, the signaling manager tsib16060 may deliver signaling information for control to a scheduler tsib16020.

General signaling information, which is not received through a separate particular channel, may be received through the DP for signaling tsib16070. Here, the DP for signaling may refer to PLS, L, etc. Here, the DP may be referred to as a PLP. A reception buffer tsib16080 may function as a buffer that receives signaling information delivered from the DP for signaling. In a decapsulation block for signaling information tsib16090, the received signaling information may be decapsulated. The decapsulated signaling information may be delivered to the signaling manager tsib16060 through a decapsulation buffer tsib16100. As described in the foregoing, the signaling manager tsib16060 may collate signaling information, and deliver the collated signaling information to a necessary part in the link layer.

The scheduler tsib16020 may determine and control operations of several modules included in the link layer. The scheduler tsib16020 may control each part of the link layer using receiver information tsib16010 and/or information delivered from the signaling manager tsib16060. In addition, the scheduler tsib16020 may determine an operation mode, etc. of each part. Here, the receiver information tsib16010 may refer to information previously stored in the receiver. The scheduler tsib16020 may use information changed by a user such as channel switching, etc. to perform a control operation.

The decapsulation part may filter a packet received from a DP tsib16110 of the physical layer, and separate a packet according to a type of the packet. It is possible to configure decapsulation parts corresponding to the number of DPs that can be simultaneously decoded in the physical layer.

The decapsulation buffer tsib16100 may function as a buffer that receives a packet stream from the physical layer to perform decapsulation. A decapsulation controller tsib16130 may determine whether to decapsulate an input packet stream. When decapsulation is performed, the packet stream may be delivered to a link layer header parser tsib16140. When decapsulation is not performed, the packet stream may be delivered to an output buffer tsib16220. The signaling information received from the scheduler tsib16020 may be used to determine whether to perform decapsulation.

The link layer header parser tsib16140 may identify a header of the delivered link layer packet. It is possible to identify a configuration of an IP packet included in a payload of the link layer packet by identifying the header. For example, the IP packet may be segmented or concatenated.

A packet configuration table tsib16150 may include payload information of segmented and/or concatenated link layer packets. The transmitter and the receiver may have the same information in the packet configuration table tsib16150. The transmitter and the receiver may refer to the information of the packet configuration table tsib16150. It is possible to find a value necessary for reassembly based on index information included in the link layer packet.

A reassembly block tsib16160 may configure payloads of the segmented and/or concatenated link layer packets as packets of an original IP stream. Segments may be collected and reconfigured as one IP packet, or concatenated packets may be separated and reconfigured as a plurality of IP packet streams. Recombined IP packets may be delivered to the overhead processing part.

The overhead processing part may perform an operation of restoring a packet subjected to overhead reduction to an original packet as a reverse operation of overhead reduction performed in the transmitter. This operation may be referred to as overhead processing. It is possible to configure overhead processing parts corresponding to the number of DPs that can be simultaneously decoded in the physical layer.

A packet recovery buffer tsib16170 may function as a buffer that receives a decapsulated RoHC packet or IP packet to perform overhead processing.

An overhead controller tsib16180 may determine whether to recover and/or decompress the decapsulated packet. When recovery and/or decompression are performed, the packet may be delivered to a packet stream recovery block tsib16190. When recovery and/or decompression are not performed, the packet may be delivered to the output buffer tsib16220. Whether to perform recovery and/or decompression may be determined based on the signaling information delivered by the scheduler tsib16020.

The packet stream recovery block tsib16190 may perform an operation of integrating a packet stream separated from the transmitter with context information of the packet stream. This operation may be a process of restoring a packet stream such that an RoHC decompressor tsib16210 can perform processing. In this process, it is possible to receive signaling information and/or context information from a signaling and/or context controller tsib16200. The signaling and/or context controller tsib16200 may determine signaling information delivered from the transmitter, and deliver the signaling information to the packet stream recovery block tsib16190 such that the signaling information may be mapped to a stream corresponding to a context ID.

The RoHC decompressor tsib16210 may restore headers of packets of the packet stream. The packets of the packet stream may be restored to forms of original IP packets through restoration of the headers. In other words, the RoHC decompressor tsib16210 may perform overhead processing.

The output buffer tsib16220 may function as a buffer before an output stream is delivered to an IP layer tsib16230.

The link layers of the transmitter and the receiver proposed in the present invention may include the blocks or modules described above. In this way, the link layer may independently operate irrespective of an upper layer and a lower layer, overhead reduction may be efficiently performed, and a supportable function according to an upper/lower layer may be easily defined/added/deleted.

FIG. 17 illustrates a configuration of signaling transmission through a link layer according to an embodiment of the present invention (transmitting/receiving sides).

In the present invention, a plurality of service providers (broadcasters) may provide services within one frequency band. In addition, a service provider may provide a plurality of services, and one service may include one or more components. It can be considered that the user receives content using a service as a unit.

The present invention presumes that a transmission protocol based on a plurality of sessions is used to support an IP hybrid broadcast. Signaling information delivered through a signaling path may be determined based on a transmission configuration of each protocol. Various names may be applied to respective protocols according to a given embodiment.

In the illustrated data configuration tsib17010 on the transmitting side, service providers (broadcasters) may provide a plurality of services (Service #1, #2, . . . ). In general, a signal for a service may be transmitted through a general transmission session (signaling C). However, the signal may be transmitted through a particular session (dedicated session) according to a given embodiment (signaling B).

Service data and service signaling information may be encapsulated according to a transmission protocol. According to a given embodiment, an IP/UDP layer may be used. According to a given embodiment, a signal in the IP/UDP layer (signaling A) may be additionally provided. This signaling may be omitted.

Data processed using the IP/UDP may be input to the link layer. As described in the foregoing, overhead reduction and/or encapsulation may be performed in the link layer. Here, link layer signaling may be additionally provided. Link layer signaling may include a system parameter, etc. Link layer signaling has been described above.

The service data and the signaling information subjected to the above process may be processed through PLPs in a physical layer. Here, a PLP may be referred to as a DP. The example illustrated in the figure presumes a case in which a base DP/PLP is used. However, depending on embodiments, transmission may be performed using only a general DP/PLP without the base DP/PLP.

In the example illustrated in the figure, a particular channel (dedicated channel) such as an FIC, an EAC, etc. is used. A signal delivered through the FIC may be referred to as a fast information table (FIT), and a signal delivered through the EAC may be referred to as an emergency alert table (EAT). The FIT may be identical to the above-described SLT. The particular channels may not be used depending on embodiments. When the particular channel (dedicated channel) is not configured, the FIT and the EAT may be transmitted using a general link layer signaling transmission scheme, or transmitted using a PLP via the IP/UDP as other service data.

According to a given embodiment, system parameters may include a transmitter-related parameter, a service provider-related parameter, etc. Link layer signaling may include IP header compression-related context information and/or identification information of data to which the context is applied. Signaling of an upper layer may include an IP address, a UDP number, service/component information, emergency alert-related information, an IP/UDP address for service signaling, a session ID, etc. Detailed examples thereof have been described above.

In the illustrated data configuration tsib17020 on the receiving side, the receiver may decode only a PLP for a corresponding service using signaling information without having to decode all PLPs.

First, when the user selects or changes a service desired to be received, the receiver may be tuned to a corresponding frequency and may read receiver information related to a corresponding channel stored in a DB, etc. The information stored in the DB, etc. of the receiver may be configured by reading an SLT at the time of initial channel scan.

After receiving the SLT and the information about the corresponding channel, information previously stored in the DB is updated, and information about a transmission path of the service selected by the user and information about a path, through which component information is acquired or a signal necessary to acquire the information is transmitted, are acquired. When the information is not determined to be changed using version information of the SLT, decoding or parsing may be omitted.

The receiver may verify whether SLT information is included in a PLP by parsing physical signaling of the PLP in a corresponding broadcast stream (not illustrated), which may be indicated through a particular field of physical signaling. It is possible to access a position at which a service layer signal of a particular service is transmitted by accessing the SLT information. The service layer signal may be encapsulated into the IP/UDP and delivered through a transmission session. It is possible to acquire information about a component included in the service using this service layer signaling. A specific SLT-SLS configuration is as described above.

In other words, it is possible to acquire transmission path information, for receiving upper layer signaling information (service signaling information) necessary to receive the service, corresponding to one of several packet streams and PLPs currently transmitted on a channel using the SLT. The transmission path information may include an IP address, a UDP port number, a session ID, a PLP ID, etc. Here, depending on embodiments, a value previously designated by the IANA or a system may be used as an IP/UDP address. The information may be acquired using a scheme of accessing a DB or a shared memory, etc.

When the link layer signal and service data are transmitted through the same PLP, or only one PLP is operated, service data delivered through the PLP may be temporarily stored in a device such as a buffer, etc. while the link layer signal is decoded.

It is possible to acquire information about a path through which the service is actually transmitted using service signaling information of a service to be received. In addition, a received packet stream may be subjected to decapsulation and header recovery using information such as overhead reduction for a PLP to be received, etc.

In the illustrated example (tsib17020), the FIC and the EAC are used, and a concept of the base DP/PLP is presumed. As described in the foregoing, concepts of the FIC, the EAC, and the base DP/PLP may not be used.

While MISO or MIMO uses two antennas in the following for convenience of description, the present invention is applicable to systems using two or more antennas. The present invention proposes a physical profile (or system) optimized to minimize receiver complexity while attaining the performance required for a particular use case. Physical (PHY) profiles (base, handheld and advanced profiles) according to an embodiment of the present invention are subsets of all configurations that a corresponding receiver should implement. The PHY profiles share most of the functional blocks but differ slightly in specific blocks and/or parameters. For the system evolution, future profiles may also be multiplexed with existing profiles in a single radio frequency (RF) channel through a future extension frame (FEF). The base profile and the handheld profile according to the embodiment of the present invention refer to profiles to which MIMO is not applied, and the advanced profile refers to a profile to which MIMO is applied. The base profile may be used as a profile for both the terrestrial broadcast service and the mobile broadcast service. That is, the base profile may be used to define a concept of a profile which includes the mobile profile. In addition, the advanced profile may be divided into an advanced profile for a base profile with MIMO and an advanced profile for a handheld profile with MIMO. Moreover, the profiles may be changed according to intention of the designer.

The following terms and definitions may be applied to the present invention. The following terms and definitions may be changed according to design.

Auxiliary stream: sequence of cells carrying data of as yet undefined modulation and coding, which may be used for future extensions or as required by broadcasters or network operators

Base data pipe: data pipe that carries service signaling data

Baseband frame (or BBFRAME): set of Kbch bits which form the input to one FEC encoding process (BCH and LDPC encoding)

Cell: modulation value that is carried by one carrier of orthogonal frequency division multiplexing (OFDM) transmission

Coded block: LDPC-encoded block of PLS1 data or one of the LDPC-encoded blocks of PLS2 data

Data pipe: logical channel in the physical layer that carries service data or related metadata, which may carry one or a plurality of service(s) or service component(s).

Data pipe unit (DPU): a basic unit for allocating data cells to a DP in a frame.

Data symbol: OFDM symbol in a frame which is not a preamble symbol (the data symbol encompasses the frame signaling symbol and frame edge symbol)

DP_ID: this 8-bit field identifies uniquely a DP within the system identified by the SYSTEM_ID

Dummy cell: cell carrying a pseudo-random value used to fill the remaining capacity not used for PLS signaling, DPs or auxiliary streams

Emergency alert channel (EAC): part of a frame that carries EAS information data

Frame: physical layer time slot that starts with a preamble and ends with a frame edge symbol

Frame repetition unit: a set of frames belonging to the same or different physical layer profiles including an FEF, which is repeated eight times in a superframe

Fast information channel (FIC): a logical channel in a frame that carries mapping information between a service and the corresponding base DP

FECBLOCK: set of LDPC-encoded bits of DP data

FFT size: nominal FFT size used for a particular mode, equal to the active symbol period Ts expressed in cycles of an elementary period T

Frame signaling symbol: OFDM symbol with higher pilot density used at the start of a frame in certain combinations of FFT size, guard interval and scattered pilot pattern, which carries a part of the PLS data

Frame edge symbol: OFDM symbol with higher pilot density used at the end of a frame in certain combinations of FFT size, guard interval and scattered pilot pattern

Frame group: the set of all frames having the same PHY profile type in a superframe

Future extension frame: physical layer time slot within the superframe that may be used for future extension, which starts with a preamble

Futurecast UTB system: proposed physical layer broadcast system, the input of which is one or more MPEG2-TS, IP or general stream(s) and the output of which is an RF signal

Input stream: a stream of data for an ensemble of services delivered to the end users by the system

Normal data symbol: data symbol excluding the frame signaling symbol and the frame edge symbol

PHY profile: subset of all configurations that a corresponding receiver should implement

PLS: physical layer signaling data including PLS1 and PLS2

PLS1: a first set of PLS data carried in a frame signaling symbol (FSS) having a fixed size, coding and modulation, which carries basic information about a system as well as parameters needed to decode PLS2

NOTE: PLS1 data remains constant for the duration of a frame group

PLS2: a second set of PLS data transmitted in the FSS, which carries more detailed PLS data about the system and the DPs

PLS2 dynamic data: PLS2 data that dynamically changes frame-by-frame

PLS2 static data: PLS2 data that remains static for the duration of a frame group

Preamble signaling data: signaling data carried by the preamble symbol and used to identify the basic mode of the system

Preamble symbol: fixed-length pilot symbol that carries basic PLS data and is located at the beginning of a frame

The preamble symbol is mainly used for fast initial band scan to detect the system signal, timing thereof, frequency offset, and FFT size.

Reserved for future use: not defined by the present document but may be defined in future

Superframe: set of eight frame repetition units

Time interleaving block (TI block): set of cells within which time interleaving is carried out, corresponding to one use of a time interleaver memory

TI group: unit over which dynamic capacity allocation for a particular DP is carried out, made up of an integer, dynamically varying number of XFECBLOCKs

NOTE: The TI group may be mapped directly to one frame or may be mapped to a plurality of frames. The TI group may contain one or more TI blocks.

Type 1 DP: DP of a frame where all DPs are mapped to the frame in time division multiplexing (TDM) scheme

Type 2 DP: DP of a frame where all DPs are mapped to the frame in frequency division multiplexing (FDM) scheme

XFECBLOCK: set of N_(cells) cells carrying all the bits of one LDPC FECBLOCK

FIG. 18 illustrates a configuration of a broadcast signal transmission apparatus for future broadcast services according to an embodiment of the present invention.

The broadcast signal transmission apparatus for future broadcast services according to the present embodiment may include an input formatting block 1000, a bit interleaved coding & modulation (BICM) block 1010, a frame building block 1020, an OFDM generation block 1030 and a signaling generation block 1040. Description will be given of an operation of each block of the broadcast signal transmission apparatus.

In input data according to an embodiment of the present invention, IP stream/packets and MPEG2-TS may be main input formats, and other stream types are handled as general streams. In addition to these data inputs, management information is input to control scheduling and allocation of the corresponding bandwidth for each input stream. In addition, the present invention allows simultaneous input of one or a plurality of TS streams, IP stream(s) and/or a general stream(s).

The input formatting block 1000 may demultiplex each input stream into one or a plurality of data pipes, to each of which independent coding and modulation are applied. A DP is the basic unit for robustness control, which affects QoS. One or a plurality of services or service components may be carried by one DP. The DP is a logical channel in a physical layer for delivering service data or related metadata capable of carrying one or a plurality of services or service components.

In addition, a DPU is a basic unit for allocating data cells to a DP in one frame.

An input to the physical layer may include one or a plurality of data streams. Each of the data streams is delivered by one DP. The input formatting block 1000 may covert a data stream input through one or more physical paths (or DPs) into a baseband frame (BBF). In this case, the input formatting block 1000 may perform null packet deletion or header compression on input data (a TS or IP input stream) in order to enhance transmission efficiency. A receiver may have a priori information for a particular part of a header, and thus this known information may be deleted from a transmitter. A null packet deletion block 3030 may be used only for a TS input stream.

In the BICM block 1010, parity data is added for error correction and encoded bit streams are mapped to complex-value constellation symbols. The symbols are interleaved across a specific interleaving depth that is used for the corresponding DP. For the advanced profile, MIMO encoding is performed in the BICM block 1010 and an additional data path is added at the output for MIMO transmission.

The frame building block 1020 may map the data cells of the input DPs into the OFDM symbols within a frame, and perform frequency interleaving for frequency-domain diversity, especially to combat frequency-selective fading channels. The frame building block 1020 may include a delay compensation block, a cell mapper and a frequency interleaver.

The delay compensation block may adjust timing between DPs and corresponding PLS data to ensure that the DPs and the corresponding PLS data are co-timed at a transmitter side. The PLS data is delayed by the same amount as the data pipes by addressing the delays of data pipes caused by the input formatting block and BICM block. The delay of the BICM block is mainly due to the time interleaver. In-band signaling data carries information of the next TI group so that the information is carried one frame ahead of the DPs to be signaled. The delay compensation block delays in-band signaling data accordingly.

The cell mapper may map PLS, DPs, auxiliary streams, dummy cells, etc. to active carriers of the OFDM symbols in the frame. The basic function of the cell mapper 7010 is to map data cells produced by the TIs for each of the DPs, PLS cells, and EAC/FIC cells, if any, into arrays of active OFDM cells corresponding to each of the OFDM symbols within a frame. A basic function of the cell mapper is to map a data cell generated by time interleaving for each DP and PLS cell to an array of active OFDM cells (if present) corresponding to respective OFDM symbols in one frame. Service signaling data (such as program specific information (PSI)/SI) may be separately gathered and sent by a DP. The cell mapper operates according to dynamic information produced by a scheduler and the configuration of a frame structure. The frequency interleaver may randomly interleave data cells received from the cell mapper to provide frequency diversity. In addition, the frequency interleaver may operate on an OFDM symbol pair including two sequential OFDM symbols using a different interleaving-seed order to obtain maximum interleaving gain in a single frame.

The OFDM generation block 1030 modulates OFDM carriers by cells produced by the frame building block, inserts pilots, and produces a time domain signal for transmission. In addition, this block subsequently inserts guard intervals, and applies peak-to-average power ratio (PAPR) reduction processing to produce a final RF signal.

Specifically, after inserting a preamble at the beginning of each frame, the OFDM generation block 1030 may apply conventional OFDM modulation having a cyclic prefix as a guard interval. For antenna space diversity, a distributed MISO scheme is applied across transmitters. In addition, a PAPR scheme is performed in the time domain. For flexible network planning, the present invention provides a set of various FFT sizes, guard interval lengths and corresponding pilot patterns.

In addition, the present invention may multiplex signals of a plurality of broadcast transmission/reception systems in the time domain such that data of two or more different broadcast transmission/reception systems providing broadcast services may be simultaneously transmitted in the same RF signal bandwidth. In this case, the two or more different broadcast transmission/reception systems refer to systems providing different broadcast services. The different broadcast services may refer to a terrestrial broadcast service, mobile broadcast service, etc.

The signaling generation block 1040 may create physical layer signaling information used for an operation of each functional block. This signaling information is also transmitted so that services of interest are properly recovered at a receiver side. Signaling information according to an embodiment of the present invention may include PLS data. PLS provides the receiver with a means to access physical layer DPs. The PLS data includes PLS1 data and PLS2 data.

The PLS1 data is a first set of PLS data carried in an FSS symbol in a frame having a fixed size, coding and modulation, which carries basic information about the system in addition to the parameters needed to decode the PLS2 data. The PLS1 data provides basic transmission parameters including parameters required to enable reception and decoding of the PLS2 data. In addition, the PLS1 data remains constant for the duration of a frame group.

The PLS2 data is a second set of PLS data transmitted in an FSS symbol, which carries more detailed PLS data about the system and the DPs. The PLS2 contains parameters that provide sufficient information for the receiver to decode a desired DP. The PLS2 signaling further includes two types of parameters, PLS2 static data (PLS2-STAT data) and PLS2 dynamic data (PLS2-DYN data). The PLS2 static data is PLS2 data that remains static for the duration of a frame group and the PLS2 dynamic data is PLS2 data that dynamically changes frame by frame. Details of the PLS data will be described later.

The above-described blocks may be omitted or replaced by blocks having similar or identical functions.

FIG. 19 illustrates a BICM block according to an embodiment of the present invention.

The BICM block illustrated in FIG. 19 corresponds to an embodiment of the BICM block 1010 described with reference to FIG. 18.

As described above, the broadcast signal transmission apparatus for future broadcast services according to the embodiment of the present invention may provide a terrestrial broadcast service, mobile broadcast service, UHDTV service, etc.

Since QoS depends on characteristics of a service provided by the broadcast signal transmission apparatus for future broadcast services according to the embodiment of the present invention, data corresponding to respective services needs to be processed using different schemes. Accordingly, the BICM block according to the embodiment of the present invention may independently process respective DPs by independently applying SISO, MISO and MIMO schemes to data pipes respectively corresponding to data paths. Consequently, the broadcast signal transmission apparatus for future broadcast services according to the embodiment of the present invention may control QoS for each service or service component transmitted through each DP.

(a) shows a BICM block applied to a profile (or system) to which MIMO is not applied, and (b) shows a BICM block of a profile (or system) to which MIMO is applied.

The BICM block to which MIMO is not applied and the BICM block to which MIMO is applied may include a plurality of processing blocks for processing each DP.

Description will be given of each processing block of the BICM block to which MIMO is not applied and the BICM block to which MIMO is applied.

A processing block 5000 of the BICM block to which MIMO is not applied may include a data FEC encoder 5010, a bit interleaver 5020, a constellation mapper 5030, a signal space diversity (SSD) encoding block 5040 and a time interleaver 5050.

The data FEC encoder 5010 performs FEC encoding on an input BBF to generate FECBLOCK procedure using outer coding (BCH) and inner coding (LDPC). The outer coding (BCH) is optional coding method. A detailed operation of the data FEC encoder 5010 will be described later.

The bit interleaver 5020 may interleave outputs of the data FEC encoder 5010 to achieve optimized performance with a combination of LDPC codes and a modulation scheme while providing an efficiently implementable structure. A detailed operation of the bit interleaver 5020 will be described later.

The constellation mapper 5030 may modulate each cell word from the bit interleaver 5020 in the base and the handheld profiles, or each cell word from the cell-word demultiplexer 5010-1 in the advanced profile using either QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, or NUQ-1024) or non-uniform constellation (NUC-16, NUC-64, NUC-256, or NUC-1024) mapping to give a power-normalized constellation point, e₁. This constellation mapping is applied only for DPs. It is observed that QAM-16 and NUQs are square shaped, while NUCs have arbitrary shapes. When each constellation is rotated by any multiple of 90 degrees, the rotated constellation exactly overlaps with its original one. This “rotation-sense” symmetric property makes the capacities and the average powers of the real and imaginary components equal to each other. Both NUQs and NUCs are defined specifically for each code rate and the particular one used is signaled by the parameter DP_MOD filed in the PLS2 data.

The time interleaver 5050 may operates at a DP level. Parameters of time interleaving (TI) may be set differently for each DP.A detailed operation of the time interleaver 5050 will be described later.

A processing block 5000-1 of the BICM block to which MIMO is applied may include the data FEC encoder, the bit interleaver, the constellation mapper, and the time interleaver.

However, the processing block 5000-1 is distinguished from the processing block 5000 of the BICM block to which MIMO is not applied in that the processing block 5000-1 further includes a cell-word demultiplexer 5010-1 and a MIMO encoding block 5020-1.

In addition, operations of the data FEC encoder, the bit interleaver, the constellation mapper, and the time interleaver in the processing block 5000-1 correspond to those of the data FEC encoder 5010, the bit interleaver 5020, the constellation mapper 5030, and the time interleaver 5050 described above, and thus description thereof is omitted.

The cell-word demultiplexer 5010-1 is used for a DP of the advanced profile to divide a single cell-word stream into dual cell-word streams for MIMO processing.

The MIMO encoding block 5020-1 may process an output of the cell-word demultiplexer 5010-1 using a MIMO encoding scheme. The MIMO encoding scheme is optimized for broadcast signal transmission. MIMO technology is a promising way to obtain a capacity increase but depends on channel characteristics. Especially for broadcasting, a strong LOS component of a channel or a difference in received signal power between two antennas caused by different signal propagation characteristics makes it difficult to obtain capacity gain from MIMO. The proposed MIMO encoding scheme overcomes this problem using rotation-based precoding and phase randomization of one of MIMO output signals.

MIMO encoding is intended for a 2×2 MIMO system requiring at least two antennas at both the transmitter and the receiver. A MIMO encoding mode of the present invention may be defined as full-rate spatial multiplexing (FR-SM). FR-SM encoding may provide capacity increase with relatively small complexity increase at the receiver side. In addition, the MIMO encoding scheme of the present invention has no restriction on an antenna polarity configuration.

MIMO processing is applied at the DP level. NUQ (e_(1,i) and e_(2,i)) corresponding to a pair of constellation mapper outputs is fed to an input of a MIMO encoder. Paired MIMO encoder output (g1,i and g2,i) is transmitted by the same carrier k and OFDM symbol l of respective TX antennas thereof.

The above-described blocks may be omitted or replaced by blocks having similar or identical functions.

FIG. 20 illustrates a BICM block according to another embodiment of the present invention.

The BICM block illustrated in FIG. 20 corresponds to another embodiment of the BICM block 1010 described with reference to FIG. 18.

FIG. 20 illustrates a BICM block for protection of physical layer signaling (PLS), an emergency alert channel (EAC) and a fast information channel (FIC). The EAC is a part of a frame that carries EAS information data, and the FIC is a logical channel in a frame that carries mapping information between a service and a corresponding base DP. Details of the EAC and FIC will be described later.

Referring to FIG. 20, the BICM block for protection of the PLS, the EAC and the FIC may include a PLS FEC encoder 6000, a bit interleaver 6010 and a constellation mapper 6020.

In addition, the PLS FEC encoder 6000 may include a scrambler, a BCH encoding/zero insertion block, an LDPC encoding block and an LDPC parity punturing block. Description will be given of each block of the BICM block.

The PLS FEC encoder 6000 may encode scrambled PLS 1/2 data, EAC and FIC sections.

The scrambler may scramble PLS1 data and PLS2 data before BCH encoding and shortened and punctured LDPC encoding.

The BCH encoding/zero insertion block may perform outer encoding on the scrambled PLS 1/2 data using a shortened BCH code for PLS protection, and insert zero bits after BCH encoding. For PLS1 data only, output bits of zero insertion may be permutted before LDPC encoding.

The LDPC encoding block may encode an output of the BCH encoding/zero insertion block using an LDPC code. To generate a complete coded block, C_(ldpc) and parity bits P_(ldpc) are encoded systematically from each zero-inserted PLS information block I_(ldpc) and appended thereto.

C _(ldpc) =[I _(ldpc) P _(ldpc) ]=[i ₀ ,i ₁ , . . . ,i _(K) _(ldpc) ⁻¹ ,p ₀ ,p ₁ , . . . ,p _(N) _(ldpc) _(−K) _(ldpc) ⁻¹]  [Equation 1]

The LDPC parity puncturing block may perform puncturing on the PLS1 data and the PLS2 data.

When shortening is applied to PLS1 data protection, some LDPC parity bits are punctured after LDPC encoding. In addition, for PLS2 data protection, LDPC parity bits of PLS2 are punctured after LDPC encoding. These punctured bits are not transmitted.

The bit interleaver 6010 may interleave each of shortened and punctured PLS1 data and PLS2 data.

The constellation mapper 6020 may map the bit-ineterleaved PLS1 data and PLS2 data to constellations.

The above-described blocks may be omitted or replaced by blocks having similar or identical functions.

FIG. 21 illustrates a bit interleaving process of PLS according to an embodiment of the present invention.

Each shortened and punctured PLS1 and PLS2 coded block is interleaved bit-by-bit as described in FIG. 22. Each block of additional parity bits is interleaved with the same block interleaving structure but separately.

In the case of BPSK, there are two branches for bit interleaving to duplicate FEC coded bits in the real and imaginary parts. Each coded block is written to the upper branch first. The bits are mapped to the lower branch by applying modulo N_(FEC) addition with cyclic shifting value floor(N_(FEC)/2), where N_(FEC) is the length of each LDPC coded block after shortening and puncturing.

In other modulation cases, such as QSPK, QAM-16 and NUQ-64, FEC coded bits are written serially into the interleaver column-wise, where the number of columns is the same as the modulation order.

In the read operation, the bits for one constellation symbol are read out sequentially row-wise and fed into the bit demultiplexer block. These operations are continued until the end of the column.

Each bit interleaved group is demultiplexed bit-by-bit in a group before constellation mapping. Depending on modulation order, there are two mapping rules. In the case of BPSK and QPSK, the reliability of bits in a symbol is equal. Therefore, the bit group read out from the bit interleaving block is mapped to a QAM symbol without any operation.

In the cases of QAM-16 and NUQ-64 mapped to a QAM symbol, the rule of operation is described in FIG. 23(a). As shown in FIG. 23(a), i is bit group index corresponding to column index in bit interleaving.

FIG. 21 shows the bit demultiplexing rule for QAM-16. This operation continues until all bit groups are read from the bit interleaving block.

FIG. 22 illustrates a configuration of a broadcast signal reception apparatus for future broadcast services according to an embodiment of the present invention.

The broadcast signal reception apparatus for future broadcast services according to the embodiment of the present invention may correspond to the broadcast signal transmission apparatus for future broadcast services described with reference to FIG. 18.

The broadcast signal reception apparatus for future broadcast services according to the embodiment of the present invention may include a synchronization & demodulation module 9000, a frame parsing module 9010, a demapping & decoding module 9020, an output processor 9030 and a signaling decoding module 9040. A description will be given of operation of each module of the broadcast signal reception apparatus.

The synchronization & demodulation module 9000 may receive input signals through m Rx antennas, perform signal detection and synchronization with respect to a system corresponding to the broadcast signal reception apparatus, and carry out demodulation corresponding to a reverse procedure of a procedure performed by the broadcast signal transmission apparatus.

The frame parsing module 9010 may parse input signal frames and extract data through which a service selected by a user is transmitted. If the broadcast signal transmission apparatus performs interleaving, the frame parsing module 9010 may carry out deinterleaving corresponding to a reverse procedure of interleaving. In this case, positions of a signal and data that need to be extracted may be obtained by decoding data output from the signaling decoding module 9040 to restore scheduling information generated by the broadcast signal transmission apparatus.

The demapping & decoding module 9020 may convert input signals into bit domain data and then deinterleave the same as necessary. The demapping & decoding module 9020 may perform demapping of mapping applied for transmission efficiency and correct an error generated on a transmission channel through decoding. In this case, the demapping & decoding module 9020 may obtain transmission parameters necessary for demapping and decoding by decoding data output from the signaling decoding module 9040.

The output processor 9030 may perform reverse procedures of various compression/signal processing procedures which are applied by the broadcast signal transmission apparatus to improve transmission efficiency. In this case, the output processor 9030 may acquire necessary control information from data output from the signaling decoding module 9040. An output of the output processor 9030 corresponds to a signal input to the broadcast signal transmission apparatus and may be MPEG-TSs, IP streams (v4 or v6) and generic streams.

The signaling decoding module 9040 may obtain PLS information from a signal demodulated by the synchronization & demodulation module 9000. As described above, the frame parsing module 9010, the demapping & decoding module 9020 and the output processor 9030 may execute functions thereof using data output from the signaling decoding module 9040.

A frame according to an embodiment of the present invention is further divided into a number of OFDM symbols and a preamble. As shown in (d), the frame includes a preamble, one or more frame signaling symbols (FSSs), normal data symbols and a frame edge symbol (FES).

The preamble is a special symbol that enables fast futurecast UTB system signal detection and provides a set of basic transmission parameters for efficient transmission and reception of a signal. Details of the preamble will be described later.

A main purpose of the FSS is to carry PLS data. For fast synchronization and channel estimation, and hence fast decoding of PLS data, the FSS has a dense pilot pattern than a normal data symbol. The FES has exactly the same pilots as the FSS, which enables frequency-only interpolation within the FES and temporal interpolation, without extrapolation, for symbols immediately preceding the FES.

FIG. 23 illustrates a signaling hierarchy structure of a frame according to an embodiment of the present invention.

FIG. 23 illustrates the signaling hierarchy structure, which is split into three main parts corresponding to preamble signaling data 11000, PLS1 data 11010 and PLS2 data 11020. A purpose of a preamble, which is carried by a preamble symbol in every frame, is to indicate a transmission type and basic transmission parameters of the frame. PLS1 enables the receiver to access and decode the PLS2 data, which contains the parameters to access a DP of interest. PLS2 is carried in every frame and split into two main parts corresponding to PLS2-STAT data and PLS2-DYN data. Static and dynamic portions of PLS2 data are followed by padding, if necessary.

Preamble signaling data according to an embodiment of the present invention carries 21 bits of information that are needed to enable the receiver to access PLS data and trace DPs within the frame structure. Details of the preamble signaling data are as follows.

FFT_SIZE: This 2-bit field indicates an FFT size of a current frame within a frame group as described in the following Table 1.

TABLE 1 Value FFT size 00  8K FFT 01 16K FFT 10 32K FFT 11 Reserved

GI_FRACTION: This 3-bit field indicates a guard interval fraction value in a current superframe as described in the following Table 2.

TABLE 2 Value GI_FRACTION 000 1/5  001 1/10 010 1/20 011 1/40 100 1/80 101  1/160 110 to 111 Reserved

EAC_FLAG: This 1-bit field indicates whether the EAC is provided in a current frame. If this field is set to ‘1’, an emergency alert service (EAS) is provided in the current frame. If this field set to ‘0’, the EAS is not carried in the current frame. This field may be switched dynamically within a superframe.

PILOT_MODE: This 1-bit field indicates whether a pilot mode is a mobile mode or a fixed mode for a current frame in a current frame group. If this field is set to ‘0’, the mobile pilot mode is used. If the field is set to ‘1’, the fixed pilot mode is used.

PAPR_FLAG: This 1-bit field indicates whether PAPR reduction is used for a current frame in a current frame group. If this field is set to a value of ‘1’, tone reservation is used for PAPR reduction. If this field is set to a value of ‘0’, PAPR reduction is not used.

RESERVED: This 7-bit field is reserved for future use.

FIG. 24 illustrates PLS1 data according to an embodiment of the present invention.

PLS1 data provides basic transmission parameters including parameters required to enable reception and decoding of PLS2. As mentioned above, the PLS1 data remain unchanged for the entire duration of one frame group. A detailed definition of the signaling fields of the PLS1 data is as follows.

PREAMBLE_DATA: This 20-bit field is a copy of preamble signaling data excluding EAC_FLAG.

NUM_FRAME_FRU: This 2-bit field indicates the number of the frames per FRU.

PAYLOAD_TYPE: This 3-bit field indicates a format of payload data carried in a frame group. PAYLOAD_TYPE is signaled as shown in Table 3.

TABLE 3 Value Payload type 1XX TS is transmitted. X1X IP stream is transmitted. XX1 GS is transmitted.

NUM_FSS: This 2-bit field indicates the number of FSSs in a current frame.

SYSTEM_VERSION: This 8-bit field indicates a version of a transmitted signal format. SYSTEM_VERSION is divided into two 4-bit fields: a major version and a minor version.

Major version: The MSB corresponding to four bits of the SYSTEM_VERSION field indicate major version information. A change in the major version field indicates a non-backward-compatible change. A default value is ‘0000’. For a version described in this standard, a value is set to ‘0000’.

Minor version: The LSB corresponding to four bits of SYSTEM_VERSION field indicate minor version information. A change in the minor version field is backwards compatible.

CELL_ID: This is a 16-bit field which uniquely identifies a geographic cell in an ATSC network. An ATSC cell coverage area may include one or more frequencies depending on the number of frequencies used per futurecast UTB system. If a value of CELL_ID is not known or unspecified, this field is set to ‘0’.

NETWORK_ID: This is a 16-bit field which uniquely identifies a current ATSC network.

SYSTEM_ID: This 16-bit field uniquely identifies the futurecast UTB system within the ATSC network. The futurecast UTB system is a terrestrial broadcast system whose input is one or more input streams (TS, IP, GS) and whose output is an RF signal. The futurecast UTB system carries one or more PHY profiles and FEF, if any. The same futurecast UTB system may carry different input streams and use different RFs in different geographical areas, allowing local service insertion. The frame structure and scheduling are controlled in one place and are identical for all transmissions within the futurecast UTB system. One or more futurecast UTB systems may have the same SYSTEM_ID meaning that they all have the same physical layer structure and configuration.

The following loop includes FRU_PHY_PROFILE, FRU_FRAME_LENGTH, FRU_GI_FRACTION, and RESERVED which are used to indicate an FRU configuration and a length of each frame type. A loop size is fixed so that four PHY profiles (including an FEF) are signaled within the FRU. If NUM_FRAME_FRU is less than 4, unused fields are filled with zeros.

FRU_PHY_PROFILE: This 3-bit field indicates a PHY profile type of an (i+1)^(th) (i is a loop index) frame of an associated FRU. This field uses the same signaling format as shown in Table 8.

FRU_FRAME_LENGTH: This 2-bit field indicates a length of an (i+1)^(th) frame of an associated FRU. Using FRU_FRAME_LENGTH together with FRU_GI_FRACTION, an exact value of a frame duration may be obtained.

FRU_GI_FRACTION: This 3-bit field indicates a guard interval fraction value of an (i+1)^(th) frame of an associated FRU. FRU_GI_FRACTION is signaled according to Table 7.

RESERVED: This 4-bit field is reserved for future use.

The following fields provide parameters for decoding the PLS2 data.

PLS2_FEC_TYPE: This 2-bit field indicates an FEC type used by PLS2 protection. The FEC type is signaled according to Table 4. Details of LDPC codes will be described later.

TABLE 4 Content PLS2 FEC type 00 4K-1/4 and 7K-3/10 LDPC codes 01 to 11 Reserved

PLS2_MOD: This 3-bit field indicates a modulation type used by PLS2. The modulation type is signaled according to Table 5.

TABLE 5 Value PLS2_MODE 000 BPSK 001 QPSK 010 QAM-16 011 NUQ-64 100 to 111 Reserved

PLS2_SIZE_CELL: This 15-bit field indicates C_(total) _(_) _(partial) _(_) _(block), a size (specified as the number of QAM cells) of the collection of full coded blocks for PLS2 that is carried in a current frame group. This value is constant during the entire duration of the current frame group.

PLS2_STAT_SIZE_BIT: This 14-bit field indicates a size, in bits, of PLS2-STAT for a current frame group. This value is constant during the entire duration of the current frame group.

PLS2_DYN_SIZE_BIT: This 14-bit field indicates a size, in bits, of PLS2-DYN for a current frame group. This value is constant during the entire duration of the current frame group.

PLS2_REP_FLAG: This 1-bit flag indicates whether a PLS2 repetition mode is used in a current frame group. When this field is set to a value of ‘1’, the PLS2 repetition mode is activated. When this field is set to a value of ‘0’, the PLS2 repetition mode is deactivated.

PLS2_REP_SIZE_CELL: This 15-bit field indicates C_(total) _(_) _(partial) _(_) _(block), a size (specified as the number of QAM cells) of the collection of partial coded blocks for PLS2 carried in every frame of a current frame group, when PLS2 repetition is used. If repetition is not used, a value of this field is equal to 0. This value is constant during the entire duration of the current frame group.

PLS2_NEXT_FEC_TYPE: This 2-bit field indicates an FEC type used for PLS2 that is carried in every frame of a next frame group. The FEC type is signaled according to Table 10.

PLS2_NEXT_MOD: This 3-bit field indicates a modulation type used for PLS2 that is carried in every frame of a next frame group. The modulation type is signaled according to Table 11.

PLS2_NEXT_REP_FLAG: This 1-bit flag indicates whether the PLS2 repetition mode is used in a next frame group. When this field is set to a value of ‘1’, the PLS2 repetition mode is activated. When this field is set to a value of ‘0’, the PLS2 repetition mode is deactivated.

PLS2_NEXT_REP_SIZE_CELL: This 15-bit field indicates C_(total) _(_) _(full) _(_) _(block), a size (specified as the number of QAM cells) of the collection of full coded blocks for PLS2 that is carried in every frame of a next frame group, when PLS2 repetition is used. If repetition is not used in the next frame group, a value of this field is equal to 0. This value is constant during the entire duration of a current frame group.

PLS2_NEXT_REP_STAT_SIZE_BIT: This 14-bit field indicates a size, in bits, of PLS2-STAT for a next frame group. This value is constant in a current frame group.

PLS2_NEXT_REP_DYN_SIZE_BIT: This 14-bit field indicates the size, in bits, of the PLS2-DYN for a next frame group. This value is constant in a current frame group.

PLS2_AP_MODE: This 2-bit field indicates whether additional parity is provided for PLS2 in a current frame group. This value is constant during the entire duration of the current frame group. Table 6 below provides values of this field. When this field is set to a value of ‘00’, additional parity is not used for the PLS2 in the current frame group.

TABLE 6 Value PLS2-AP mode 00 AP is not provided 01 AP1 mode 10 to 11 Reserved

PLS2_AP_SIZE_CELL: This 15-bit field indicates a size (specified as the number of QAM cells) of additional parity bits of PLS2. This value is constant during the entire duration of a current frame group.

PLS2_NEXT_AP_MODE: This 2-bit field indicates whether additional parity is provided for PLS2 signaling in every frame of a next frame group. This value is constant during the entire duration of a current frame group. Table 12 defines values of this field.

PLS2_NEXT_AP_SIZE_CELL: This 15-bit field indicates a size (specified as the number of QAM cells) of additional parity bits of PLS2 in every frame of a next frame group. This value is constant during the entire duration of a current frame group.

RESERVED: This 32-bit field is reserved for future use.

CRC_32: A 32-bit error detection code, which is applied to all PLS1 signaling.

FIG. 25 illustrates PLS2 data according to an embodiment of the present invention.

FIG. 25 illustrates PLS2-STAT data of the PLS2 data. The PLS2-STAT data is the same within a frame group, while PLS2-DYN data provides information that is specific for a current frame.

Details of fields of the PLS2-STAT data are described below.

FIC_FLAG: This 1-bit field indicates whether the FIC is used in a current frame group. If this field is set to ‘1’, the FIC is provided in the current frame. If this field set to ‘0’, the FIC is not carried in the current frame. This value is constant during the entire duration of a current frame group.

AUX_FLAG: This 1-bit field indicates whether an auxiliary stream is used in a current frame group. If this field is set to ‘1’, the auxiliary stream is provided in a current frame. If this field set to ‘0’, the auxiliary stream is not carried in the current frame. This value is constant during the entire duration of current frame group.

NUM_DP: This 6-bit field indicates the number of DPs carried within a current frame. A value of this field ranges from 1 to 64, and the number of DPs is NUM_DP+1.

DP_ID: This 6-bit field identifies uniquely a DP within a PHY profile.

DP_TYPE: This 3-bit field indicates a type of a DP. This is signaled according to the following Table 7.

TABLE 7 Value DP Type 000 DP Type 1 001 DP Type 2 010 to 111 Reserved

DP_GROUP_ID: This 8-bit field identifies a DP group with which a current DP is associated. This may be used by the receiver to access DPs of service components associated with a particular service having the same DP_GROUP_ID.

BASE_DP_ID: This 6-bit field indicates a DP carrying service signaling data (such as PSI/SI) used in a management layer. The DP indicated by BASE_DP_ID may be either a normal DP carrying the service signaling data along with service data or a dedicated DP carrying only the service signaling data.

DP_FEC_TYPE: This 2-bit field indicates an FEC type used by an associated DP. The FEC type is signaled according to the following Table 8.

TABLE 8 Value FEC_TYPE 00 16K LDPC 01 64K LDPC 10 to 11 Reserved

DP_COD: This 4-bit field indicates a code rate used by an associated DP. The code rate is signaled according to the following Table 9.

TABLE 9 Value Code rate 0000 5/15 0001 6/15 0010 7/15 0011 8/15 0100 9/15 0101 10/15  0110 11/15  0111 12/15  1000 13/15  1001 to 1111 Reserved

DP_MOD: This 4-bit field indicates modulation used by an associated DP. The modulation is signaled according to the following Table 10.

TABLE 10 Value Modulation 0000 QPSK 0001 QAM-16 0010 NUQ-64 0011 NUQ-256 0100 NUQ-1024 0101 NUC-16 0110 NUC-64 0111 NUC-256 1000 NUC-1024 1001 to 1111 Reserved

DP_SSD_FLAG: This 1-bit field indicates whether an SSD mode is used in an associated DP. If this field is set to a value of ‘1’, SSD is used. If this field is set to a value of ‘0’, SSD is not used.

The following field appears only if PHY_PROFILE is equal to ‘010’, which indicates the advanced profile:

DP_MIMO: This 3-bit field indicates which type of MIMO encoding process is applied to an associated DP. A type of MIMO encoding process is signaled according to the following Table 11.

TABLE 11 Value MIMO encoding 000 FR-SM 001 FRFD-SM 010 to 111 Reserved

DP_TI_TYPE: This 1-bit field indicates a type of time interleaving. A value of ‘0’ indicates that one TI group corresponds to one frame and contains one or more TI blocks. A value of ‘1’ indicates that one TI group is carried in more than one frame and contains only one TI block.

DP_TI_LENGTH: The use of this 2-bit field (allowed values are only 1, 2, 4, and 8) is determined by values set within the DP_TI_TYPE field as follows.

If DP_TI_TYPE is set to a value of ‘1’, this field indicates P_(I), the number of frames to which each TI group is mapped, and one TI block is present per TI group (N_(TI)=1). Allowed values of P_(I) with the 2-bit field are defined in Table 12 below.

If DP_TI_TYPE is set to a value of ‘0’, this field indicates the number of TI blocks N_(TI) per TI group, and one TI group is present per frame (P_(I)=1). Allowed values of P_(I) with the 2-bit field are defined in the following Table 12.

TABLE 12 2-bit field P_(I) N_(TI) 00 1 1 01 2 2 10 4 3 11 8 4

DP_FRAME_INTERVAL: This 2-bit field indicates a frame interval (I_(JUMP)) within a frame group for an associated DP and allowed values are 1, 2, 4, and 8 (the corresponding 2-bit field is ‘00’, ‘01’, ‘10’, or ‘11’, respectively). For DPs that do not appear every frame of the frame group, a value of this field is equal to an interval between successive frames. For example, if a DP appears on frames 1, 5, 9, 13, etc., this field is set to a value of ‘4’. For DPs that appear in every frame, this field is set to a value of ‘1’.

DP_TI_BYPASS: This 1-bit field determines availability of the time interleaver 5050. If time interleaving is not used for a DP, a value of this field is set to ‘1’. If time interleaving is used, the value is set to ‘0’.

DP_FIRST_FRAME_IDX: This 5-bit field indicates an index of a first frame of a superframe in which a current DP occurs. A value of DP_FIRST_FRAME_IDX ranges from 0 to 31.

DP_NUM_BLOCK_MAX: This 10-bit field indicates a maximum value of DP_NUM_BLOCKS for this DP. A value of this field has the same range as DP_NUM_BLOCKS.

DP_PAYLOAD_TYPE: This 2-bit field indicates a type of payload data carried by a given DP. DP_PAYLOAD_TYPE is signaled according to the following Table 13.

TABLE 13 Value Payload type 00 TS 01 IP 10 GS 11 Reserved

DP_INBAND_MODE: This 2-bit field indicates whether a current DP carries in-band signaling information. An in-band signaling type is signaled according to the following Table 14.

TABLE 14 Value In-band mode 00 In-band signaling is not carried. 01 INBAND-PLS is carried 10 INBAND-ISSY is carried 11 INBAND-PLS and INBAND-ISSY are carried

DP_PROTOCOL_TYPE: This 2-bit field indicates a protocol type of a payload carried by a given DP. The protocol type is signaled according to Table 15 below when input payload types are selected.

TABLE 15 If If If DP_PAY- DP_PAY- DP_PAY- LOAD_TYPE LOAD_TYPE LOAD_TYPE Value is TS is IP is GS 00 MPEG2-TS IPv4 (Note) 01 Reserved IPv6 Reserved 10 Reserved Reserved Reserved 11 Reserved Reserved Reserved

DP_CRC_MODE: This 2-bit field indicates whether CRC encoding is used in an input formatting block. A CRC mode is signaled according to the following Table 16.

TABLE 16 Value CRC mode 00 Not used 01 CRC-8 10 CRC-16 11 CRC-32

DNP_MODE: This 2-bit field indicates a null-packet deletion mode used by an associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). DNP_MODE is signaled according to Table 17 below. If DP_PAYLOAD_TYPE is not TS (‘00’), DNP_MODE is set to a value of ‘00’.

TABLE 17 Value Null-packet deletion mode 00 Not used 01 DNP-NORMAL 10 DNP-OFFSET 11 Reserved

ISSY_MODE: This 2-bit field indicates an ISSY mode used by an associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). ISSY_MODE is signaled according to Table 18 below. If DP_PAYLOAD_TYPE is not TS (‘00’), ISSY_MODE is set to the value of ‘00’.

TABLE 18 Value ISSY mode 00 Not used 01 ISSY-UP 10 ISSY-BBF 11 Reserved

HC_MODE_TS: This 2-bit field indicates a TS header compression mode used by an associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). HC_MODE_TS is signaled according to the following Table 19.

TABLE 19 Value Header compression mode 00 HC_MODE_TS 1 01 HC_MODE_TS 2 10 HC_MODE_TS 3 11 HC_MODE_TS 4

HC_MODE_IP: This 2-bit field indicates an IP header compression mode when DP_PAYLOAD_TYPE is set to IP (‘01’). HC_MODE_IP is signaled according to the following Table 20.

TABLE 20 Value Header compression mode 00 No compression 01 HC_MODE_IP 1 10 to 11 Reserved

PID: This 13-bit field indicates the PID number for TS header compression when DP_PAYLOAD_TYPE is set to TS (‘00’) and HC_MODE_TS is set to ‘01’ or ‘10’.

RESERVED: This 8-bit field is reserved for future use.

The following fields appear only if FIC_FLAG is equal to ‘1’.

FIC_VERSION: This 8-bit field indicates the version number of the FIC.

FIC_LENGTH_BYTE: This 13-bit field indicates the length, in bytes, of the FIC.

RESERVED: This 8-bit field is reserved for future use.

The following fields appear only if AUX_FLAG is equal to ‘1’.

NUM_AUX: This 4-bit field indicates the number of auxiliary streams. Zero means no auxiliary stream is used.

AUX_CONFIG_RFU: This 8-bit field is reserved for future use.

AUX_STREAM_TYPE: This 4-bit is reserved for future use for indicating a type of a current auxiliary stream.

AUX_PRIVATE_CONFIG: This 28-bit field is reserved for future use for signaling auxiliary streams.

FIG. 26 illustrates PLS2 data according to another embodiment of the present invention.

FIG. 26 illustrates PLS2-DYN data of the PLS2 data. Values of the PLS2-DYN data may change during the duration of one frame group while sizes of fields remain constant.

Details of fields of the PLS2-DYN data are as below.

FRAME_INDEX: This 5-bit field indicates a frame index of a current frame within a superframe. An index of a first frame of the superframe is set to ‘0’.

PLS_CHANGE_COUNTER: This 4-bit field indicates the number of superframes before a configuration changes. A next superframe with changes in the configuration is indicated by a value signaled within this field. If this field is set to a value of ‘0000’, it means that no scheduled change is foreseen. For example, a value of ‘1’ indicates that there is a change in the next superframe.

FIC_CHANGE_COUNTER: This 4-bit field indicates the number of superframes before a configuration (i.e., content of the FIC) changes. A next superframe with changes in the configuration is indicated by a value signaled within this field. If this field is set to a value of ‘0000’, it means that no scheduled change is foreseen. For example, a value of ‘0001’ indicates that there is a change in the next superframe.

RESERVED: This 16-bit field is reserved for future use.

The following fields appear in a loop over NUM_DP, which describe parameters associated with a DP carried in a current frame.

DP_ID: This 6-bit field uniquely indicates a DP within a PHY profile.

DP_START: This 15-bit (or 13-bit) field indicates a start position of the first of the DPs using a DPU addressing scheme. The DP_START field has differing length according to the PHY profile and FFT size as shown in the following Table 21.

TABLE 21 DP_START field size PHY profile 64K 16K Base 13 bits 15 bits Handheld — 13 bits Advanced 13 bits 15 its

DP_NUM_BLOCK: This 10-bit field indicates the number of FEC blocks in a current TI group for a current DP.

DP_NUM_BLOCK: This 10-bit field indicates the number of FEC blocks in a current TI group for a current DP. A value of DP_NUM_BLOCK ranges from 0 to 1023.

RESERVED: This 8-bit field is reserved for future use.

The following fields indicate FIC parameters associated with the EAC.

EAC_FLAG: This 1-bit field indicates the presence of the EAC in a current frame. This bit is the same value as EAC_FLAG in a preamble.

EAS_WAKE_UP_VERSION_NUM: This 8-bit field indicates a version number of a wake-up indication.

If the EAC_FLAG field is equal to ‘1’, the following 12 bits are allocated to EAC_LENGTH_BYTE. If the EAC_FLAG field is equal to ‘0’, the following 12 bits are allocated to EAC_COUNTER.

EAC_LENGTH_BYTE: This 12-bit field indicates a length, in bytes, of the EAC.

EAC_COUNTER: This 12-bit field indicates the number of frames before a frame where the EAC arrives.

The following fields appear only if the AUX_FLAG field is equal to ‘1’.

AUX_PRIVATE_DYN: This 48-bit field is reserved for future use for signaling auxiliary streams. A meaning of this field depends on a value of AUX_STREAM_TYPE in a configurable PLS2-STAT.

CRC_32: A 32-bit error detection code, which is applied to the entire PLS2.

FIG. 27 illustrates a logical structure of a frame according to an embodiment of the present invention.

As above mentioned, the PLS, EAC, FIC, DPs, auxiliary streams and dummy cells are mapped to the active carriers of OFDM symbols in a frame. PLS1 and PLS2 are first mapped to one or more FSSs. Thereafter, EAC cells, if any, are mapped to an immediately following PLS field, followed next by FIC cells, if any. The DPs are mapped next after the PLS or after the EAC or the FIC, if any. Type 1 DPs are mapped first and Type 2 DPs are mapped next. Details of types of the DPs will be described later. In some cases, DPs may carry some special data for EAS or service signaling data. The auxiliary streams or streams, if any, follow the DPs, which in turn are followed by dummy cells. When the PLS, EAC, FIC, DPs, auxiliary streams and dummy data cells are mapped all together in the above mentioned order, i.e. the PLS, EAC, FIC, DPs, auxiliary streams and dummy data cells, cell capacity in the frame is exactly filled.

FIG. 28 illustrates PLS mapping according to an embodiment of the present invention.

PLS cells are mapped to active carriers of FSS(s). Depending on the number of cells occupied by PLS, one or more symbols are designated as FSS(s), and the number of FSS(s) N_(F)SS is signaled by NUM_FSS in PLS1. The FSS is a special symbol for carrying PLS cells. Since robustness and latency are critical issues in the PLS, the FSS(s) have higher pilot density, allowing fast synchronization and frequency-only interpolation within the FSS.

PLS cells are mapped to active carriers of the FSS(s) in a top-down manner as shown in the figure. PLS1 cells are mapped first from a first cell of a first FSS in increasing order of cell index. PLS2 cells follow immediately after a last cell of PLS1 and mapping continues downward until a last cell index of the first FSS. If the total number of required PLS cells exceeds the number of active carriers of one FSS, mapping proceeds to a next FSS and continues in exactly the same manner as the first FSS.

After PLS mapping is completed, DPs are carried next. If an EAC, an FIC or both are present in a current frame, the EAC and the FIC are placed between the PLS and “normal” DPs.

Hereinafter, description will be given of encoding an FEC structure according to an embodiment of the present invention. As above mentioned, the data FEC encoder may perform FEC encoding on an input BBF to generate an FECBLOCK procedure using outer coding (BCH), and inner coding (LDPC). The illustrated FEC structure corresponds to the FECBLOCK. In addition, the FECBLOCK and the FEC structure have same value corresponding to a length of an LDPC codeword.

As described above, BCH encoding is applied to each BBF (K_(bch) bits), and then LDPC encoding is applied to BCH-encoded BBF (K_(ldpc) bits=N_(bch) bits).

A value of N_(ldpc) is either 64,800 bits (long FECBLOCK) or 16,200 bits (short FECBLOCK).

Table 22 and Table 23 below show FEC encoding parameters for the long FECBLOCK and the short FECBLOCK, respectively.

TABLE 22 BCH error correction LDPC rate N_(ldpc) K_(ldpc) K_(bch) capability N_(bch) − K_(bch) 5/15 64800 21600 21408 12 192 6/15 25920 25728 7/15 30240 30048 8/15 34560 34368 9/15 38880 38688 10/15  43200 43008 11/15  47520 47328 12/15  51840 51648 13/15  56160 55968

TABLE 23 BCH error correction LDPC rate N_(ldpc) K_(ldpc) K_(bch) capability N_(bch) − K_(bch) 5/15 16200 5400 5232 12 168 6/15 6480 6312 7/15 7560 7392 8/15 8640 8472 9/15 9720 9552 10/15  10800 10632 11/15  11880 11712 12/15  12960 12792 13/15  14040 13872

Detailed operations of BCH encoding and LDPC encoding are as below.

A 12-error correcting BCH code is used for outer encoding of the BBF. A BCH generator polynomial for the short FECBLOCK and the long FECBLOCK are obtained by multiplying all polynomials together.

LDPC code is used to encode an output of outer BCH encoding. To generate a completed B_(ldpc) (FECBLOCK), P_(ldpc) (parity bits) is encoded systematically from each I_(ldpc) (BCH—encoded BBF), and appended to I_(ldpc). The completed B_(ldpc) (FECBLOCK) is expressed by the following Equation.

B _(ldpc) =[I _(ldpc) P _(ldpc) ]=[i ₀ ,i ₁ , . . . ,i _(K) _(ldpc) ⁻¹ ,p ₀ ,p ₁ , . . . ,p _(N) _(ldpc) _(−K) _(ldpc) ⁻¹]  [Equation 2]

Parameters for the long FECBLOCK and the short FECBLOCK are given in the above Tables 22 and 23, respectively.

A detailed procedure to calculate N_(ldpc)−K_(ldpc) parity bits for the long FECBLOCK, is as follows.

1) Initialize the parity bits

p ₀ =p ₁ =p ₂ = . . . =p _(N) _(ldpc) _(−K) _(ldpc) ⁻¹  [Equation 3]

2) Accumulate a first information bit—i₀, at a parity bit address specified in a first row of addresses of a parity check matrix. Details of the addresses of the parity check matrix will be described later. For example, for the rate of 13/15,

$\begin{matrix} \begin{matrix} {p_{983} = {p_{983} \oplus i_{0}}} & {p_{2815} = {p_{2815} \oplus i_{0}}} \\ {p_{4837} = {p_{4837} \oplus i_{0}}} & {p_{4989} = {p_{4989} \oplus i_{0}}} \\ {p_{6138} = {p_{6138} \oplus i_{0}}} & {p_{6458} = {p_{6458} \oplus i_{0}}} \\ {p_{6921} = {p_{6921} \oplus i_{0}}} & {p_{6974} = {p_{6974} \oplus i_{0}}} \\ {p_{7572} = {p_{7572} \oplus i_{0}}} & {p_{2860} = {p_{8260} \oplus i_{0}}} \\ {p_{8496} = {p_{8496} \oplus i_{0}}} & \; \end{matrix} & \left\lbrack {{Equation}\mspace{14mu} 4} \right\rbrack \end{matrix}$

3) For the next 359 information bits, i_(s), s=1, 2, . . . , 359, accumulate i_(s) at parity bit addresses using following Equation.

{x+(s mod 360)×Q _(ldpc)} mod(N _(ldpc) −K _(ldpc))  [Equation 5]

Here, x denotes an address of a parity bit accumulator corresponding to a first bit i₀, and Q_(ldpc) is a code rate dependent constant specified in the addresses of the parity check matrix. Continuing with the example, Q_(ldpc)=24 for the rate of 13/15, so for an information bit it, the following operations are performed.

$\begin{matrix} \begin{matrix} {p_{1007} = {p_{1007} \oplus i_{1}}} & {p_{2839} = {p_{2839} \oplus i_{1}}} \\ {p_{4861} = {p_{4861} \oplus i_{1}}} & {p_{5013} = {p_{5013} \oplus i_{1}}} \\ {p_{6162} = {p_{6162} \oplus i_{1}}} & {p_{6482} = {p_{6482} \oplus i_{1}}} \\ {p_{6945} = {p_{6945} \oplus i_{1}}} & {p_{6998} = {p_{6998} \oplus i_{1}}} \\ {p_{7596} = {p_{7596} \oplus i_{1}}} & {p_{8284} = {p_{8284} \oplus i_{1}}} \\ {p_{8520} = {p_{8520} \oplus i_{1}}} & \; \end{matrix} & \left\lbrack {{Equation}\mspace{14mu} 6} \right\rbrack \end{matrix}$

4) For a 361th information bit i₃₆₀, an address of the parity bit accumulator is given in a second row of the addresses of the parity check matrix. In a similar manner, addresses of the parity bit accumulator for the following 359 information bits i_(s), s=361, 362, . . . , 719 are obtained using Equation 6, where x denotes an address of the parity bit accumulator corresponding to the information bit i₃₆₀, i.e., an entry in the second row of the addresses of the parity check matrix.

5) In a similar manner, for every group of 360 new information bits, a new row from the addresses of the parity check matrix is used to find the address of the parity bit accumulator.

After all of the information bits are exhausted, a final parity bit is obtained as below.

6) Sequentially perform the following operations starting with i=1.

p _(i) =p _(i) ⊕p _(i−1) ,i=1,2, . . . ,N _(ldpc) −K _(ldpc)−1  [Equation 7]

Here, final content of p_(i) (i=0, 1, . . . , N_(ldpc)−K_(ldpc)−1) is equal to a parity bit p_(i).

TABLE 24 Code rate Q_(ldpc) 5/15 120 6/15 108 7/15 96 8/15 84 9/15 72 10/15  60 11/15  48 12/15  36 13/15  24

This LDPC encoding procedure for the short FECBLOCK is in accordance with t LDPC encoding procedure for the long FECBLOCK, except that Table 24 is replaced with Table 25, and the addresses of the parity check matrix for the long FECBLOCK are replaced with the addresses of the parity check matrix for the short FECBLOCK.

TABLE 25 Code rate Q_(ldpc) 5/15 30 6/15 27 7/15 24 8/15 21 9/15 18 10/15  15 11/15  12 12/15  9 13/15  6

FIG. 29 illustrates time interleaving according to an embodiment of the present invention.

(a) to (c) show examples of a TI mode.

A time interleaver operates at the DP level. Parameters of time interleaving (TI) may be set differently for each DP.

The following parameters, which appear in part of the PLS2-STAT data, configure the TI.

DP_TI_TYPE (allowed values: 0 or 1): This parameter represents the TI mode. The value of ‘0’ indicates a mode with multiple TI blocks (more than one TI block) per TI group. In this case, one TI group is directly mapped to one frame (no inter-frame interleaving). The value of ‘1’ indicates a mode with only one TI block per TI group. In this case, the TI block may be spread over more than one frame (inter-frame interleaving).

DP_TI_LENGTH: If DP_TI_TYPE=‘0’, this parameter is the number of TI blocks N_(TI) per TI group. For DP_TI_TYPE=‘1’, this parameter is the number of frames P_(I) spread from one TI group.

DP_NUM_BLOCK_MAX (allowed values: 0 to 1023): This parameter represents the maximum number of XFECBLOCKs per TI group.

DP_FRAME_INTERVAL (allowed values: 1, 2, 4, and 8): This parameter represents the number of the frames I_(JUMP) between two successive frames carrying the same DP of a given PHY profile.

DP_TI_BYPASS (allowed values: 0 or 1): If time interleaving is not used for a DP, this parameter is set to ‘1’. This parameter is set to ‘0’ if time interleaving is used.

Additionally, the parameter DP_NUM_BLOCK from the PLS2-DYN data is used to represent the number of XFECBLOCKs carried by one TI group of the DP.

When time interleaving is not used for a DP, the following TI group, time interleaving operation, and TI mode are not considered. However, the delay compensation block for the dynamic configuration information from the scheduler may still be required. In each DP, the XFECBLOCKs received from SSD/MIMO encoding are grouped into TI groups. That is, each TI group is a set of an integer number of XFECBLOCKs and contains a dynamically variable number of XFECBLOCKs. The number of XFECBLOCKs in the TI group of index n is denoted by N_(xBLOCK) _(_) _(Group)(n) and is signaled as DP_NUM_BLOCK in the PLS2-DYN data. Note that N_(xBLOCK) _(_) _(Group)(n) may vary from a minimum value of 0 to a maximum value of N_(xBLOCK) _(_) _(Group) _(_) _(MAX) (corresponding to DP_NUM_BLOCK_MAX), the largest value of which is 1023.

Each TI group is either mapped directly to one frame or spread over P_(I) frames. Each TI group is also divided into more than one TI block (N_(TI)), where each TI block corresponds to one usage of a time interleaver memory. The TI blocks within the TI group may contain slightly different numbers of XFECBLOCKs. If the TI group is divided into multiple TI blocks, the TI group is directly mapped to only one frame. There are three options for time interleaving (except an extra option of skipping time interleaving) as shown in the following Table 26.

TABLE 26 Modes Descriptions Op- Each TI group contains one TI block and is mapped directly to tion 1 one frame as shown in (a). This option is signaled in PLS2- STAT by DP_TI_TYPE = ‘0’ and DP_TI_LENGTH = ‘1’ (N_(TI) = 1). Op- Each TI group contains one TI block and is mapped to more than tion 2 one frame. (b) shows an example, where one TI group is mapped to two frames, i.e., DP_TI_LENGTH = ‘2’ (P_(I) = 2) and DP_FRAME_INTERVAL (I_(JUMP) = 2). This provides greater time diversity for low data-rate services. This option is signaled in PLS2-STAT by DP_TI_TYPE = ‘1’. Op- Each TI group is divided into multiple TI blocks and is mapped tion 3 directly to one frame as shown in (c). Each TI block may use a full TI memory so as to provide a maximum bit-rate for a DP. This option is signaled in PLS2-STAT by DP_TI_TYPE = ‘0’ and DP_TI_LENGTH = N_(TI), while P_(I) = 1.

Typically, the time interleaver may also function as a buffer for DP data prior to a process of frame building. This is achieved by means of two memory banks for each DP. A first TI block is written to a first bank. A second TI block is written to a second bank while the first bank is being read from and so on.

The TI is a twisted row-column block interleaver. For an s^(th) TI block of an n^(th) TI group, the number of rows N_(r) of a TI memory is equal to the number of cells N_(cells), i.e., N_(r)=N_(cells) while the number of columns N_(c) is equal to the number N_(xBLOCK) _(_) _(TI)(n,s).

FIG. 30 illustrates a basic operation of a twisted row-column block interleaver according to an embodiment of the present invention.

FIG. 30(a) shows a write operation in the time interleaver and FIG. 30(b) shows a read operation in the time interleaver. A first XFECBLOCK is written column-wise into a first column of a TI memory, and a second XFECBLOCK is written into a next column, and so on as shown in (a). Then, in an interleaving array, cells are read diagonal-wise. During diagonal-wise reading from a first row (rightwards along a row beginning with a left-most column) to a last row, N_(r) cells are read out as shown in (b). In detail, assuming z_(n,s,i) (i=0, . . . , N_(r)N_(c)) as a TI memory cell position to be read sequentially, a reading process in such an interleaving array is performed by calculating a row index R_(n,s,i), a column index C_(n,s,i), and an associated twisting parameter T_(n,s,i) as in the following Equation.

[Equation 8] GENERATE(R_(n,s,i), C_(n,s,i)) = { R_(n,s,i) = mod(i, N_(r)), T_(n,s,i) = mod(S_(shift) × R_(n,s,i), N_(c)), $C_{n,s,i} = {{mod}\left( {{T_{n,s,i} + \left\lfloor \frac{i}{N_{r}} \right\rfloor},N_{c}} \right)}$ }

Here, S_(shift) is a common shift value for a diagonal-wise reading process regardless of N_(xBLOCK) _(_) _(TI)(n,s), and the shift value is determined by N_(xBLOCK) _(_) _(TI) _(_) _(MAX) given in PLS2-STAT as in the following Equation.

$\begin{matrix} {{for}\left\{ {\begin{matrix} \begin{matrix} {{N_{xBlock}^{\prime}\text{?}_{TI}\text{?}_{MAX}} =} \\ {{{N_{xBlock}\text{?}_{TI}\text{?}_{MAX}} + 1},} \end{matrix} & {\mspace{11mu} \begin{matrix} {{if}\mspace{14mu} N_{xBlock}\text{?}_{TI}\text{?}_{MAX}} \\ {{{mod}\mspace{11mu} 2} = 0} \end{matrix}} \\ \begin{matrix} {{N_{xBlock}^{\prime}\text{?}_{TI}\text{?}_{MAX}} =} \\ {{N_{xBlock}\text{?}_{TI}\text{?}_{MAX}},} \end{matrix} & {\begin{matrix} {{if}\mspace{14mu} N_{xBlock}\text{?}_{TI}\text{?}_{MAX}} \\ {{{mod}\mspace{11mu} 2} = 1} \end{matrix}\mspace{11mu}} \end{matrix},{S_{shift} = {\frac{{{N_{xBlock}^{\prime}\text{?}_{TI}\text{?}_{MAX}} - 1}\;}{2}\text{?}\text{indicates text missing or illegible when filed}}}} \right.} & \left\lbrack {{Equation}\mspace{14mu} 9} \right\rbrack \end{matrix}$

As a result, cell positions to be read are calculated by coordinates z_(n,s,i)=N_(r)C_(n,s,i)+R_(n,s,i).

FIG. 31 illustrates an operation of a twisted row-column block interleaver according to another embodiment of the present invention.

More specifically, FIG. 31 illustrates an interleaving array in a TI memory for each TI group, including virtual XFECBLOCKs when N_(xBLOCK) _(_) _(TI)(0,0)=3, N_(xBLOCK) _(_) _(TI)(1,0)=6, and N_(xBLOCK TI)(2,0)=5

A variable number N_(xBLOCK) _(_) _(TI)(n,s)=N_(r) may be less than or equal to N′_(xBLOCK) _(_) _(TI) _(_) _(MAX). Thus, in order to achieve single-memory deinterleaving at a receiver side regardless of N_(xBLOCK) _(_) _(TI)(n,s), the interleaving array for use in the twisted row-column block interleaver is set to a size of N_(r)×N_(c)=N_(cells)×N′_(xBLOCK) _(_) _(TI) _(_) _(MAX) by inserting the virtual XFECBLOCKs into the TI memory and a reading process is accomplished as in the following Equation.

[Equation 10] p = 0; for i = 0;i < N_(cells)N_(xBLOCK) _(—) _(TI) _(—) _(MAX)′;i = i + 1 {GENERATE (R_(n,s,i), C_(n,s,i)); V_(i) = N_(r)C_(n,s,j) + R_(n,s,j)  if V_(i) < N_(cells)N_(xBLOCK) _(—) _(TI)(n,s)  {   Z_(n,s,p) = V_(i); p = p + 1;   } }

The number of TI groups is set to 3. An option of the time interleaver is signaled in the PLS2-STAT data by DP_TI_TYPE=‘0’, DP_FRAME_INTERVAL=‘1’, and DP_TI_LENGTH=‘1’, i.e., NTI=1, IJUMP=1, and PI=1. The number of XFECBLOCKs, each of which has Ncells=30 cells, per TI group is signaled in the PLS2-DYN data by NxBLOCK_TI(0,0)=3, NxBLOCK_TI(1,0)=6, and NxBLOCK_TI(2,0)=5, respectively. A maximum number of XFECBLOCKs is signaled in the PLS2-STAT data by NxBLOCK_Group_MAX, which leads to └N_(xBLOCK) _(_) _(Group) _(_) _(MAX)/N_(TI)┘=N_(xBLOCK) _(_) _(TI) _(_) _(MAX)=6.

The purpose of the Frequency Interleaver, which operates on data corresponding to a single OFDM symbol, is to provide frequency diversity by randomly interleaving data cells received from the frame builder. In order to get maximum interleaving gain in a single frame, a different interleaving-sequence is used for every OFDM symbol pair comprised of two sequential OFDM symbols.

Therefore, the frequency interleaver according to the present embodiment may include an interleaving address generator for generating an interleaving address for applying corresponding data to a symbol pair.

FIG. 32 illustrates an interleaving address generator including a main pseudo-random binary sequence (PRBS) generator and a sub-PRBS generator according to each FFT mode according to an embodiment of the present invention.

(a) shows the block diagrams of the interleaving-address generator for 8K FFT mode, (b) shows the block diagrams of the interleaving-address generator for 16K FFT mode and (c) shows the block diagrams of the interleaving-address generator for 32K FFT mode.

The interleaving process for the OFDM symbol pair is described as follows, exploiting a single interleaving-sequence. First, available data cells (the output cells from the Cell Mapper) to be interleaved in one OFDM symbol O_(m,l) is defined as O_(m,l)=└x_(m,l,0), . . . , x_(m,l,p), . . . , x_(m,l,N) _(data) ⁻¹┘ for l=0, . . . , N_(sym)−1, where x_(m,l,p) is the p^(th) cell of the l^(th) OFDM symbol in the m^(th) frame and N_(data) is the number of data cells: N_(data)=C_(FSS) for the frame signaling symbol(s), N_(data)=C_(data) for the normal data, and N_(data)=C_(FES) for the frame edge symbol. In addition, the interleaved data cells are defined as P_(m,l)=└ν_(m,l,0), . . . , ν_(m,l,N) _(data) ⁻¹┘ for l=0, . . . , N_(sym)−1.

For the OFDM symbol pair, the interleaved OFDM symbol pair is given by ν_(m,l,H) _(l) _((p))=x_(m,l,p), p=0, . . . , N_(data)−1, for the first OFDM symbol of each pair ν_(m,l,p)=x_(m,l,H) _(l) _((p)), p=0, . . . , N_(data)−1, for the second OFDM symbol of each pair, where H_(l)(p) is the interleaving

address generated by a PRBS generator.

FIG. 33 illustrates a main PRBS used for all FFT modes according to an embodiment of the present invention.

(a) illustrates the main PRBS, and (b) illustrates a parameter Nmax for each FFT mode.

FIG. 34 illustrates a sub-PRBS used for FFT modes and an interleaving address for frequency interleaving according to an embodiment of the present invention.

(a) illustrates a sub-PRBS generator, and (b) illustrates an interleaving address for frequency interleaving. A cyclic shift value according to an embodiment of the present invention may be referred to as a symbol offset.

FIG. 35 illustrates a write operation of a time interleaver according to an embodiment of the present invention.

FIG. 35 illustrates a write operation for two TI groups.

A left block in the figure illustrates a TI memory address array, and right blocks in the figure illustrate a write operation when two virtual FEC blocks and one virtual FEC block are inserted into heads of two contiguous TI groups, respectively.

Hereinafter, description will be given of a configuration of a time interleaver and a time interleaving method using both a convolutional interleaver (CI) and a block interleaver (BI) or selectively using either the CI or the BI according to a physical layer pipe (PLP) mode. A PLP according to an embodiment of the present invention is a physical path corresponding to the same concept as that of the above-described DP, and a name of the PLP may be changed by a designer.

A PLP mode according to an embodiment of the present invention may include a single PLP mode or a multi-PLP mode according to the number of PLPs processed by a broadcast signal transmitter or a broadcast signal transmission apparatus. The single PLP mode corresponds to a case in which one PLP is processed by the broadcast signal transmission apparatus. The single PLP mode may be referred to as a single PLP.

The multi-PLP mode corresponds to a case in which one or more PLPs are processed by the broadcast signal transmission apparatus. The multi-PLP mode may be referred to as multiple PLPs.

In the present invention, time interleaving in which different time interleaving schemes are applied according to PLP modes may be referred to as hybrid time interleaving. Hybrid time interleaving according to an embodiment of the present invention is applied for each PLP (or at each PLP level) in the multi-PLP mode.

FIG. 36 illustrates an interleaving type applied according to the number of PLPs in a table.

In a time interleaving according to an embodiment of the present invention, an interleaving type may be determined based on a value of PLP_NUM. PLP_NUM is a signaling field indicating a PLP mode. When PLP_NUM has a value of 1, the PLP mode corresponds to a single PLP. The single PLP according to the present embodiment may be applied only to a CI.

When PLP_NUM has a value greater than 1, the PLP mode corresponds to multiple PLPs. The multiple PLPs according to the present embodiment may be applied to the CI and a BI. In this case, the CI may perform inter-frame interleaving, and the BI may perform intra-frame interleaving.

FIG. 37 is a block diagram including a first example of a structure of a hybrid time interleaver described above.

The hybrid time interleaver according to the first example may include a BI and a CI. The time interleaver of the present invention may be positioned between a BICM chain block and a frame builder.

The BICM chain block illustrated in FIGS. 37 and 38 may include the blocks in the processing block 5000 of the BICM block illustrated in FIG. 19 except for the time interleaver 5050. The frame builder illustrated in FIGS. 37 and 38 may perform the same function as that of the frame building block 1020 of FIG. 18.

As described in the foregoing, it is possible to determine whether to apply the BI according to the first example of the structure of the hybrid time interleaver depending on values of PLP_NUM. That is, when PLP_NUM=1, the BI is not applied (BI is turned OFF) and only the CI is applied. When PLP_NUM>1, both the BI and the CI may be applied (BI is turned ON). A structure and an operation of the CI applied when PLP_NUM>1 may be the same as or similar to a structure and an operation of the CI applied when PLP_NUM=1.

FIG. 38 is a block diagram including a second example of the structure of the hybrid time interleaver described above.

An operation of each block included in the second example of the structure of the hybrid time interleaver is the same as the above description in FIG. 20. It is possible to determine whether to apply a BI according to the second example of the structure of the hybrid time interleaver depending on values of PLP_NUM. Each block of the hybrid time interleaver according to the second example may perform operations according to embodiments of the present invention. In this instance, an applied structure and operation of a CI may be different between a case of PLP_NUM=1 and a case of PLP_NUM>1.

FIG. 39 is a block diagram including a first example of a structure of a hybrid time deinterleaver.

The hybrid time deinterleaver according to the first example may perform an operation corresponding to a reverse operation of the hybrid time interleaver according to the first example described above. Therefore, the hybrid time deinterleaver according to the first example of FIG. 39 may include a convolutional deinterleaver (CDI) and a block deinterleaver (BDI).

A structure and an operation of the CDI applied when PLP_NUM>1 may be the same as or similar to a structure and an operation of the CDI applied when PLP_NUM=1.

It is possible to determine whether to apply the BDI according to the first example of the structure of the hybrid time deinterleaver depending on values of PLP_NUM. That is, when PLP_NUM=1, the BDI is not applied (BDI is turned OFF) and only the CDI is applied.

The CDI of the hybrid time deinterleaver may perform inter-frame deinterleaving, and the BDEI may perform intra-frame deinterleaving. Details of inter-frame deinterleaving and intra-frame deinterleaving are the same as the above description.

A BICM decoding block illustrated in FIGS. 39 and 40 may perform a reverse operation of the BICM chain block of FIGS. 37 and 38.

FIG. 40 is a block diagram including a second example of the structure of the hybrid time deinterleaver.

The hybrid time deinterleaver according to the second example may perform an operation corresponding to a reverse operation of the hybrid time interleaver according to the second example described above. An operation of each block included in the second example of the structure of the hybrid time deinterleaver may be the same as the above description in FIG. 39.

It is possible to determine whether to apply a BDI according to the second example of the structure of the hybrid time deinterleaver depending on values of PLP_NUM. Each block of the hybrid time deinterleaver according to the second example may perform operations according to embodiments of the present invention. In this instance, an applied structure and operation of a CDI may be different between a case of PLP_NUM=1 and a case of PLP_NUM>1.

FIG. 41 is a block diagram illustrating a hybrid broadcast reception apparatus according to an embodiment of the present invention. A hybrid broadcast system can transmit broadcast signals in connection with terrestrial broadcast networks and the Internet. The hybrid broadcast reception apparatus can receive broadcast signals through terrestrial broadcast networks (broadcast networks) and the Internet (broadband). The hybrid broadcast reception apparatus may include physical layer module(s), physical layer I/F module(s), service/content acquisition controller, Internet access control module(s), a signaling decoder, a service signaling manager, a service guide manager, an application signaling manager, an alert signal manager, an alert signaling parser, a targeting signaling parser, a streaming media engine, a non-real time file processor, a component synchronizer, a targeting processor, an application processor, an A/V processor, a device manager, a data sharing and communication unit, redistribution module(s), companion device(s) and/or an external management module.

The physical layer module(s) can receive a broadcast related signal through a terrestrial broadcast channel, process the received signal, convert the processed signal into an appropriate format and deliver the signal to the physical layer I/F module(s).

The physical layer I/F module(s) can acquire an IP datagram from information obtained from the physical layer module. In addition, the physical layer I/F module can convert the acquired IP datagram into a specific frame (e.g., RS frame, GSE, etc.).

The service/content acquisition controller can perform control operation for acquisition of services, content and signaling data related thereto through broadcast channels and/or broadband channels.

The Internet access control module(s) can control receiver operations for acquiring service, content, etc. through broadband channels.

The signaling decoder can decode signaling information acquired through broadcast channels.

The service signaling manager can extract signaling information related to service scan and/or content from the IP datagram, parse the extracted signaling information and manage the signaling information.

The service guide manager can extract announcement information from the IP datagram, manage a service guide (SG) database and provide a service guide.

The application signaling manager can extract signaling information related to application acquisition from the IP datagram, parse the signaling information and manage the signaling information.

The alert signaling parser can extract signaling information related to alerting from the IP datagram, parse the extracted signaling information and manage the signaling information.

The targeting signaling parser can extract signaling information related to service/content personalization or targeting from the IP datagram, parse the extracted signaling information and manage the signaling information. In addition, the targeting signaling parser can deliver the parsed signaling information to the targeting processor.

The streaming media engine can extract audio/video data for A/V streaming from the IP datagram and decode the audio/video data.

The non-real time file processor can extract NRT data and file type data such as applications, decode and manage the extracted data.

The component synchronizer can synchronize content and services such as streaming audio/video data and NRT data.

The targeting processor can process operations related to service/content personalization on the basis of the targeting signaling data received from the targeting signaling parser.

The application processor can process application related information and downloaded application state and represent parameters.

The A/V processor can perform audio/video rendering related operations on the basis of decoded audio/video data and application data.

The device manager can perform connection and data exchange with external devices. In addition, the device manager can perform operations of managing external devices connectable thereto, such as addition/deletion/update of the external devices.

The data sharing and communication unit can process information related to data transmission and exchange between a hybrid broadcast receiver and external devices. Here, data that can be transmitted and exchanged between the hybrid broadcast receiver and external devices may be signaling data, A/V data and the like.

The redistribution module(s) can acquire information related to future broadcast services and content when the broadcast receiver cannot directly receive terrestrial broadcast signals. In addition, the redistribution module can support acquisition of future broadcast services and content by future broadcast systems when the broadcast receiver cannot directly receive terrestrial broadcast signals.

The companion device(s) can share audio, video or signaling data by being connected to the broadcast receiver according to the present invention. The companion device may be an external device connected to the broadcast receiver.

The external management module can refer to a module for broadcast services/content provision. For example, the external management module can be a future broadcast services/content server. The external management module may be an external device connected to the broadcast receiver.

FIG. 42 is a block diagram illustrating a hybrid broadcast receiver according to an embodiment of the present invention.

The hybrid broadcast receiver can receive hybrid broadcast services through interworking of terrestrial broadcasting and a broadband network in DTV services of a future broadcast system. The hybrid broadcast receiver can receive broadcast audio/video (A/V) content transmitted through terrestrial broadcasting and receive enhancement data related thereto or part of broadcast A/V content through the broadband network in real time. In the specification, the broadcast A/V content can be referred to as media content.

The hybrid broadcast receiver may include a physical layer controller D55010, a tuner D55020, a physical frame parser D55030, a link layer frame parser D55040, an IP/UDP datagram filter D55050, an ATSC 3.0 digital TV (DTV) control engine D55060, an ALC/LCT+ client D55070, a timing controller D55080, a signaling parser D55090, a dynamic adaptive streaming over HTTP (DASH) client D55100, an HTTP access client D55110, an ISO base media file format (BMFF) parser D55120 and/or a media decoder D55130.

The physical layer controller D55010 can control operations of the tuner D55020 and the physical frame parser D55030 using radio frequency (RF) information of a terrestrial broadcast channel that the hybrid broadcast receiver intends to receive.

The tuner D55020 can receive a broadcast related signal through a terrestrial broadcast channel, process the received signal and convert the signal into an appropriate format. For example, the tuner D55020 can convert a received terrestrial broadcast signal into physical frames.

The physical frame parser D55030 can parse a received physical frame and acquire a link layer frame through processing related thereto.

The link layer parser D55040 can execute related operations for acquisition of link layer signaling or an IP/UDP datagram from the link layer frame. The link layer parser D55040 can output at least one IP/UDP datagram.

The IP/UDP datagram filter D55050 can filter a specific IP/UDP datagram from the received at least one IP/UDP datagram. That is, the IP/UDP datagram filter D55050 can selectively filter an IP/UDP datagram, which is selected by the ATSC 3.0 DTV control engine, from the at least one IP/UDP datagram output from the link layer parser D55040. The IP/UDP datagram filter D55050 can output an application layer transport protocol packet such as ALC/LCT+.

The ATSC 3.0 DTV control engine D55060 can serve as an interface between modules included in the hybrid broadcast receiver. In addition, the ATSC 3.0 DTV control engine D55060 can deliver parameters necessary for each module to each module and control operation of each module through the parameters. In the present invention, the ATSC 3.0 DTV control engine D55060 can transfer media presentation description (MPD) and/or an MPD URL to the DASH client D55100. In addition, the ATSC 3.0 DTV control engine D55060 can transfer a delivery mode and/or a transport session identifier (TSI) to the ALC/LCT+ client D55070. Here, the TSI indicates an identifier of a session in which a transport packet including a signaling message such as MPD or MPD URL related signaling is transmitted, for example, ALC/LCT+ session corresponding to application layer transport protocol or FLUTE session. In addition, the TSI can correspond to an asset ID of an MMT.

The ALC/LCT+ client D55070 can generate one or more ISO base media file format (ISO MMFF) objects by processing an application layer transport protocol packet such as ALC/LCT+ and collecting and processing a plurality of packets. The application layer transport protocol packet may include an ALC/LCT packet, an ALC/LCT+ packet, a ROUTE packet and/or an MMTP packet.

The timing controller D55080 can process a packet including system time information and control a system clock according thereto.

The signaling parser D55090 can acquire and parse DTV broadcast service related signaling, and generate and manage a channel map on the basis of the parsed signaling. In the present invention, the signaling parser can parse MPD or MPD related information extended from signaling information.

The DASH client D55100 can execute operations related to real-time streaming or adaptive streaming. The DASH client D55100 can receive DASH content from an HTTP server through the HTTP access client D55110. The DASH client D55100 can process a received DASH segment and output an ISO BMFF object. In the present invention, the DASH client D55100 can deliver a fully qualified representation ID or a segment URL to the ATSC 3.0 DTV control engine D55060. Here, the fully qualified representation ID can refer to an ID corresponding to a combination of an MPD URL, period@id and represenstation@id, for example. In addition, the DASH client D55100 can receive the MPD or MPD URL from the ATSC 3.0 DTV control engine D55060. The DASH client D55100 can receive a desired media stream or DASH segment from the HTTP server using the received MPD or MPD URL. In the specification, the DASH client D55100 may be referred to as a processor.

The HTTP access client D55110 can request that the HTTP server provide specific information, receive a response to the request from the HTTP server and process the response. Here, the HTTP server can process the request received from the HTTP access client and provide a response to the request.

The ISO BMFF parser D55120 can extract audio/video data from the ISO BMFF object.

The media decoder D55130 can decode the received audio/video data and perform processing for presentation of the decoded audio/video data.

To provide hybrid broadcast services through interworking of a terrestrial broadcast network and a broadband network according to the hybrid broadcast receiver of the present invention, MPD needs to be extended or modified. The aforementioned terrestrial broadcast system can transmit extended or modified MPD and the hybrid broadcast receiver can receive content through broadcasting or a broadband network using the extended or modified MPD. That is, the hybrid broadcast receiver can receive the extended or modified MPD through terrestrial broadcasting and receive content through terrestrial broadcasting or a broadband network on the basis of the MPD. A description will be given of elements or attributes that need to be additionally included in the extended or modified MPD, compared to the conventional MPD. In the following, the extended or modified MPD is referred to as MPD.

The MPD can be extended or modified to represent ATSC 3.0 service. The extended or modified MPD can additionally include MPD@anchorPresentationTime, Common@presentable, Common.Targeting, Common.TargetDevice and/or Common@associatedTo.

MPD@anchorPresentationTime can indicate presentation time anchor of segments included in the MPD, that is, base time. In the following, MPD@anchorPresentationTime can be used as effective time of the MPD. MPD@anchorPresentationTime can indicate the earliest playback time from among segments included in the MPD.

The MPD may further include common attributes and elements. The common attributes and elements can be applied to AdaptionSet and Representation in the MPD. Common@presentable can indicate that media described by the MPD is a presentable component.

Common.Targeting can indicate targeting properties and/or personalization properties of the media described by the MPD.

Common.TargetDevice can indicate a target device or target devices of the media described by the MPD.

Common@associatedTo can indicate adaptationSet and/or representation related to the media described by the MPD.

In addition, MPD@id, Period@id and AdaptationSet@id included in the MPD may be necessary to specify media content described by the MPD. That is, the DASH client can specify content to be received on the basis of the MPD using MPD@id, Period@id and AdaptationSet@id and signal the content to the ATSC 3.0 DTV control engine. The ATSC 3.0 DTV control engine can receive the corresponding content and deliver the content to the DASH client.

FIG. 43 illustrates a protocol stack of a future hybrid broadcast system according to an embodiment of the present invention. As shown in the figure, a future broadcast transmission system supporting IP based hybrid broadcasting can encapsulate audio or video data of broadcast services in the ISO base media file format (BMFF). Here, a DASH segment or a media processing unit (MPU) of an MMT can be used for encapsulation. In addition, the future broadcast system can equally transmit the encapsulated data through a broadcast network and the Internet or differently transmit the encapsulated data through the broadcast network and the Internet according to attributes of the respective networks. Furthermore, the future broadcast system can equally transmit the encapsulated data using at least one of broadcast or broadband. In the case of a broadcast network using broadcast, the broadcast system can transmit data encapsulated in the ISO BMFF through an application layer transport protocol packet which supports real-time object transmission. For example, the broadcast system can encapsulate data in a real-time object delivery over unidirectional transport (ROUTE) or MMTP transport packet. The broadcast system can process the encapsulated data into an IP/UDP datagram, load the IP/UDP datagram in a broadcast signal and transmit the broadcast signal. When broadband is used, the broadcast system can deliver the encapsulated data to a receiving side through streaming such as DASH.

In addition, the broadcast system can transmit broadcast service signaling information as follows. In the case of a broadcast network using broadcast, the broadcast system can transmit signaling information through physical layers of the future broadcast transmission system and the broadcast network according to signaling attributes. Here, the broadcast system can transmit the signaling information through a specific data pipe (DP) of a transport frame included in a broadcast signal. Signaling information transmitted through broadcast may have a form of being encapsulated in a bitstream or IP/UDP datagram. When broadband is used, the broadcast system can return and deliver signaling data to a receiver in response to a request of the receiver.

In addition, the broadcast system can transmit broadcast service ESG or NRT content through the following method. In the case of a broadcast network using broadcast, the broadcast system can encapsulate the ESG or NRT content in an application layer transport protocol packet, for example, real-time object delivery over unidirectional transport (ROUTE) or MMTP transport packet. The broadcast system can generate an IP/UDP datagram with the encapsulated ESG or NRT content, load the IP/UDP datagram in a broadcast signal and transmit the broadcast signal. When broadband is used, the broadcast system can return and deliver the ESG or NRT content to a receiver in response to a request of the receiver.

FIG. 44 illustrates a structure of a transport frame delivered to a physical layer of the future broadcast transmission system according to an embodiment of the present invention. The future broadcast system can transmit a transport frame using broadcast. In the figure, P1 located at the front of the transport frame can refer to a symbol including information for transport signal detection. P1 can include tuning information and a receiver can decode a part L1 following P1 on the basis of a parameter included in the symbol P1. The broadcast system can include, in the part L1, information about transport frame configuration and characteristics of data pipes. That is, the receiver can obtain the information about the transport frame configuration and characteristics of data pipes by decoding the part L1. In addition, the receiver can acquire information that needs to be shared between DPs through a common DP. According to an embodiment, the transport frame may not include the common DP.

Components such as audio, video and data in the transport frame are included in an interleaved DP region composed of DP1 to DPn and transmitted. Here, DPs through which components constituting each service (channel) are transmitted can be signaled through L1 or a common PLP.

In addition, the future broadcast system can transmit information for rapidly acquiring information about services included in a transport frame. That is, the future broadcast system enables a future broadcast receiver to rapidly acquire broadcast services and content related information included in a transport frame. When services/content generated by one or more broadcasting stations are present in the corresponding frame, the future broadcast system can enable the receiver to efficiently recognize the services/content according to the broadcasting stations. That is, the future broadcast system can include, in a transport stream, service list information about services included in the transport stream, and transmit the transport stream including the service list information.

When an additional channel, for example, a fast information channel (FIC) is present, the broadcast system can transmit broadcast service related information through the additional channel such that the receiver can rapidly scan broadcast services and content in a corresponding frequency. As shown in FIG. 44, the broadcast system can include, in the transport stream, information for broadcast service scan and acquisition and transmit the same. Here, the region including the information for broadcast service scan and acquisition may be referred to as an FIC. The receiver can acquire information about broadcast services generated and transmitted by one or more broadcasting stations and easily and rapidly scan broadcast services available therein using the information.

In addition, a specific DP included in the transport stream can serve as a base DP capable of rapidly and robustly delivering signaling about broadcast services and content transmitted in the corresponding transport frame. Data transmitted through each DP of the transport frame of the physical layer is as shown in the lower part of FIG. 44. That is, link layer signaling or an IP datagram can be encapsulated in a generic packet in a specific format and then transmitted through a DP. Here, the IP datagram can include signaling data. Link (low) layer signaling can include signaling related to fast service scan/acquisition, context information of IP header compression and emergency alert.

FIG. 45 illustrates a transport packet of an application layer transport protocol according to an embodiment of the present invention. An application layer transport session can be composed of a combination of an IP address and a port number. When the application layer transport protocol corresponds to ROUTE, a ROUTE session can be composed of one or more layered coding transport (LCT) sessions. For example, when a single media component (e.g., DASH representation) is delivered through a single LCT transport session, one or more media components can be multiplexed and delivered through a single application transport session. Furthermore, one or more transport objects can be delivered through a single LCT transport session, and each transport object can be a DASH segment associated with DASH representation delivered through the transport session.

For example, when the application layer transport protocol is an LCT based protocol, a transport packet can be configured as follows. The transport packet can include an LCT header, a ROUTE header and payload data. A plurality of fields included in the transport packet is as follows.

The LCT header can include the following fields. A version field V can indicate version information of the corresponding transport protocol packet. A field C can include a flag related to the length of a congestion control information field which will be described below. A field PSI can indicate protocol-specific information, that is, information specific to the corresponding protocol. A field S can indicate a flag associated with the length of a transport session identifier (TSI) field. A field O can indicate a flag associated with the length of a transport object identifier (TOI) field. A field H can indicate whether a half-word (16 bits) is added to the lengths of the TSI field and the TOI field. A field A (close session flag) can indicate that a session is closed or closure of the session is imminent. A field B (close object flag) can indicate that an object being transmitted is closed or closure of the object is imminent. A code point field can indicate information related to encoding or decoding of a payload of the corresponding packet. For example, payload type can correspond to the information. A congestion control information field can indicate information related to congestion control. For example, the information related to congestion control can be a current time slot index (CTSI), a channel number or a packet sequence number in the corresponding channel. A transport session identifier field can indicate a transport field identifier. A transport object identifier field can indicate an identifier of an object transmitted through the corresponding transport session.

A ROUTE(ALC) header can include additional information of the preceding LCT header, such as a payload identifier related to a forward error correction scheme.

Payload data can indicate a data part of the payload of the corresponding packet.

FIG. 46 illustrates a method for transmitting signaling data by the future broadcast system according to an embodiment of the present invention. Signaling data of the future broadcast system can be transmitted as shown in the figure. To enable the receiver to support fast service/content scan and acquisition, the future broadcast transmission system can transmit signaling data with respect to a broadcast service delivered through a corresponding physical layer frame, via a fast information channel (FIC). In the specification, the FIC can refer to information about a service list. Unless an additional FIC is present, the signaling data may be delivered through a path through which link layer signaling is delivered. That is, signaling information including information about services and components (audio and video) thereof can be encapsulated in an IP/UDP datagram and transmitted through one or more DPs in the physical layer frame. According to an embodiment, signaling information about services and service components can be encapsulated in an application layer transport packet (e.g. a ROUTE packet or an MMTP packet) and transmitted.

The upper part of FIG. 46 illustrates an example of delivering the aforementioned signaling data through an FIC or one or more DPs. That is, signaling data for supporting fast service scan/acquisition can be delivered through the FIC and signaling data including detailed information about services can be encapsulated in an IP datagram and transmitted through a specific DP. In the specification, the signaling data including detailed information about services may be referred to as service layer signaling.

The middle part of FIG. 46 illustrates an example of delivering the aforementioned signaling data through an FIC and one or more DPs. That is, signaling data for supporting fast service scan/acquisition can be delivered through the FIC and signaling data including detailed information about services can be encapsulated in an IP datagram and transmitted through a specific DP. In addition, part of signaling data including information about a specific component included in a service may be delivered through one or more transport sessions in the application layer transport protocol. For example, part of the signaling data can be delivered through one or more transport sessions in a ROUTE session.

The lower part of FIG. 46 illustrates an example of delivering the aforementioned signaling data through an FIC and one or more DPs. That is, signaling data for supporting fast service scan/acquisition can be delivered through the FIC and signaling data including detailed information about services can be delivered through one or more sessions in a ROUTE session.

FIG. 47 illustrates a syntax of a fast information table (FIT) according to an embodiment of the present invention.

In the present invention, the FIT may be referred to as an FIC, SLT or low level signaling (LLS). In addition, the FIT may be defined as a signaling structure included in LLS. In this case, some information included in the FIT according to an embodiment of the present invention can be included in the LLS. The LLS corresponds to signaling information delivered through a payload of an IP packet having a well-known address/port in a broadcast system.

The illustrated FIT may correspond to a signaling structure for supporting broadcast service scan and acquisition in a receiver. Broadcast services and/or content generated by one or more broadcast stations may be delivered through a specific frequency. In this case, information necessary for this procedure may be signaled through the FIT such that the receiver can rapidly and easily scan broadcasting stations corresponding to the frequency and/or services and/or content of the broadcast stations.

When a signaling structure proposed by the present invention is used, the receiver can scan services and a service acquisition speed of the receiver can be reduced. While the syntax of the illustrated FIT is described, information included in the FIT may be represented in other formats such as XML.

According to the present invention, the FIT may be delivered through a fast information channel (FIC) which is a separate channel in a physical layer transport frame. Otherwise, the FIT may be delivered through a common DP through which information that can be shared between data pipes of the physical layer can be delivered. Information included in the FIT may be delivered through a link layer signaling delivery path or link layer signaling, which is defined in the link layer. Otherwise, the FIT may be delivered through a service signaling channel through which service signaling is transmitted or a transport session of the application layer.

The FIT according to an embodiment of the present invention may include FIT_protocol_version information, broadcast_stream_id information, FIT_data_version information, FIT_length information, num_providers information, esg_service_id information, signaling_on_inet_flag information, provider_id information, inet_server_URL_length information, inet_server_URL[k] information, num_services information, service_id information, SLS_data_version information, service_category information, short_service_name_length information, short_service_name information, sp_indicator information, service_status information, SLS_simpleservice information, capability_flag information, signaling_broadcast_flag information, capability_code information, a signaling_broadcast_info( ) element, num_service_level_descriptor information, a service_level_descriptor( ) element, num_FIT_level_descriptor information, an FIT_level_descriptor( ) element and/or a CRC( ) element.

The FIT_protocol_version information can indicate the protocol version of the FIT. When the protocol related to the FIT is changed, the FIT_protocol_version information can indicates such protocol change.

The FIT_data_version information can indicate the data version of the FIT. When data in the FIT is changed, the FIT_data_version information can indicate such data change.

FIT_length information indicates the length (size) of information subordinate to the FIT. The FIT_length can indicate the length (or size) of the FIT.

The num_providers information indicates the number of broadcasters providing the FIT or broadcasters providing services. The num_providers information may indicate the number of broadcasters providing an ESG service.

The esg_service_id information is an identifier for identifying the ESG service which provides an ESG. The esg_service_id information can be used separately from the aforementioned service_id information.

The signaling_on_inet_flag information indicates whether signaling information related to the ESG service is delivered through the Internet. The signaling_on_inet_flag information indicates whether service level signaling is delivered through a broadband network.

The provider_id information identifies a broadcaster which provides the ESG service.

The inet_server_URL_length information can indicate the length of the URL of a server which provides signaling information related to the ESG service.

The inet_server_URL[k] information can indicate the URL of a server which provides signaling information or service level signaling related to the ESG service.

The SLS_data_version information can indicate the data version of service level signaling.

The SLS_simpleservice information can indicate whether signaling which replaces SLS is transmitted in a layer in which the FIT is delivered. For example, in the case of a specific service, the receiver can configure signaling such that the corresponding service can be accessed using only information included in the FIT before information of SLS is used. In this case, the SLS_simpleservice information can indicate whether the corresponding service can be accessed using only information included in the FIT. The SLS_simpleservice information can indicate whether the corresponding service is a simple broadcast service. The SLS_simpleservice information can indicate whether all components included in the corresponding service are delivered through a broadcast network or some components are delivered through a broadband network. That is, the SLS_simpleservice information indicates whether the receiver needs to access the broadband network in order to effectively present one or more broadcast services.

The capability_flag information indicates whether capability related information is included in the FIT.

The signaling_broadcast_flag information can indicate whether service level signaling is delivered through a broadband network.

The capability_code information indicates receiver capabilities necessary to decode a component in a service to enable significant presentation of the component.

The signaling_broadcast_info( ) element can include information necessary to acquire service level signaling when the service level signaling is delivered through a broadcast network. The signaling_broadcast_info( ) element can include information indicating a location, address and/or region through which the service level signaling is delivered and/or information indicating a protocol used to deliver the service level signaling.

The num_FIT_level_descriptor information indicates the number of descriptors defined in the level (or layer) in which the FIT is delivered.

The FIT_level_descriptor element includes descriptors defined in the level (or layer) in which the FIT is delivered.

The CRC( ) element can include information related to a CRC.

Information and/or elements which are not described in FIG. 47, from among information and/or elements included in the FIT, correspond to information/elements having the same names included in the aforementioned FIC, FIT, SLT and/or LLS and thus description thereof is omitted.

FIG. 48 illustrates description about information included in the FIT according to an embodiment of the present invention.

The FIT may include FIT_protocol_version information, Broadcast_stream_id information, FIT_data_version information, FIT_length information, num_providers information, esg_service_id information, signaling_on_inet_flag information, provider_id information, inet_server_URL_length information, inet_server_URL[k] information, num_services information, service_id information, SLS_data_version information, service_category information, short_service_name_length information, short_service_name information, sp_indicator information, service_status information, SLS_simpleservice information, capability_flag information, signaling_broadcast_flag information, capability_code information, a signaling_broadcast_info( ) element, num_service_level_descriptor information, a service_level_descriptor( ) element, num_FIT_level_descriptor information, an FIT_level_descriptor( ) element and/or a CRC( ) element.

The above information and/or elements correspond to the aforementioned information/elements and thus description thereof is omitted.

FIG. 49 illustrates a signaling connecting structure in a procedure in which the receiver acquires a service according to an embodiment of the present invention.

The receiver parses an FIT delivered through the physical layer (or the first layer). The receiver recognizes whether an FIT of a new version is delivered by parsing the FIT_version information and parses the FIT when the new FIT is delivered.

In the present embodiment, when the FIT_version information has a value of “002”, the receiver checks the signaling_broadcast_flag information and/or information in the signaling_broadcast_info ( ) element and acquires service level signaling.

In the present embodiment, when the FIT_version information has a value of “03”, the receiver can select a broadcaster which provides the service using the provider_id information. The receiver can receive service level signaling related to the service provided by the corresponding broadcaster through a broadband network (Internet) using the signaling_over_inet_flag information and/or information in the signaling_over_inet_information ( ) element. The receiver may check the signaling_broadcast_flag information and/or information in the signaling_broadcast_info ( ) element and acquire service level signaling.

In the present embodiment, SLS with respect to service 1 (Srv1) is delivered through a broadcast network, whereas SLS with respect to service 2 (Srv2) is delivered through a broadband network. Since LLS including the FIT can be delivered through a predetermined region or location in a broadcast signal, as described above, the receiver can acquire the LLS and/or the FIT from the corresponding region or location.

FIG. 50 illustrates a syntax of an FIT according to another embodiment of the present invention.

The FIT according to another embodiment of the present invention may include FIT_protocol_version information, broadcast_stream_id information, FIT_data_version information, FIT_length information, num_providers information, num_services information, service_id information, SLS_data_version information, service_category information, short_service_name_length information, short_service_name information, sp_indicator information, service_status information, SLS_simpleservice information, num_service_level_descriptor information, a service_level_descriptor( ) element, num_provider_level_descriptor information, a provider_level_descriptor( ) element, num_FIT_level_descriptor information, an FIT_level_descriptor( ) information and/or a CRC( ) element.

The FIT according to another embodiment of the present invention includes the num_provider_level_descriptor information and the provider_level_descriptor( ) element in addition to the aforementioned FIT and presents loops for performing signaling per provider (broadcaster) and per service.

The num_provider_level_descriptor information indicates the number of descriptors which provide information related to a broadcaster.

The provider_level_descriptor( ) element can include a descriptor providing information related to the broadcaster.

According to the present embodiment, even when a plurality of broadcasters is present, it is possible to signal information for acquiring services provided by the respective broadcasters using the signaling structure of the same FIT.

Information and/or elements which are not described in FIG. 47, from among information and/or elements included in the FIT, correspond to information/elements having the same names included in the aforementioned FIC, FIT, SLT and/or LLS and thus description thereof is omitted.

FIG. 51 is a table showing descriptor type and locations at which descriptors can be included according to an embodiment of the present invention.

The aforementioned signaling structure may include a capability_descriptor, a signaling_broadcast_descriptor and/or a signaling_over_internet_descriptor.

The capability_descriptor can include signaling information which specifies capabilities required for the receiver to effectively present a service, content and/or a component. The capability_descriptor is a service level descriptor and can be included in an FIT or an SLT.

The signaling_broadcast_descriptor can include information necessary to bootstrap (acquire) service level signaling included in a broadcast signal and delivered. The signaling_broadcast_descriptor can include information indicating source IP addresses, destination IP addresses and/or destination ports of packets which deliver the service level signaling. The signaling_broadcast_descriptor can include SLS_PLP_ID corresponding to information identifying a PLP through which the service level signaling is delivered and/or SLS_TSI information identifying a TSI of a transport session through which the service level signaling is delivered. The SLS_PLP_ID information can be included in a signaling structure delivered in the link layer as necessary.

The signaling_over_internet_descriptor can include information indicating whether the service level signaling can be delivered through the Internet and/or address information of a server which provides the service level signaling.

FIG. 52 illustrates a signaling_broadcast_descriptor according to an embodiment of the present invention.

The signaling_broadcast_descriptor according to the present embodiment may include descriptor_tag information, descriptor_length information, IP_version_flag information, SLS_src_IP_addr_flag information, SLS_src_IP_addr information, SLS_dst_IP_addr information, SLS_dst_port_num information, SLS_TSI information and/or SLS_PLP_id information.

The descriptor_tag information specifies the corresponding descriptor.

The descriptor_length information indicates the length of the descriptor.

The IP_version_flag information indicates the IP version used for an IP address delivered in the descriptor.

The SLS_src_IP_addr_flag information indicates whether the SLS_src_IP_addr information is present.

The SLS_src_IP_addr information indicates source IP addresses of packets which deliver SLS.

The SLS_dst_IP_addr information indicates destination IP addresses of packets which deliver SLS.

The SLS_dst_port_num information indicates destination port numbers of packets which deliver SLS.

The SLS_TSI information identifies a transport session through which SLS is delivered.

The SLS_PLP_id information identifies a location/region in which SLS is delivered. The SLS_PLP_id information indicates a PLP including the SLS. The SLS_PLP_id information may be included in link layer signaling and delivered.

FIG. 53 illustrates meaning of the signaling_on_inet_descriptor (or signaling_over_internet_descriptor) and values of the inet_server_URL_type information according to an embodiment of the present invention.

The signaling_on_inet_descriptor may include descriptor_tag information, descriptor_length information, num_inet_URL information, inet_server_URL_type information, inet_server_URL_length information and/or inet_server_URL information.

The descriptor_tag information identifies the corresponding descriptor.

The descriptor_length information indicates the length of the descriptor.

The num_inet_URL information indicates the number of Internet URL addresses signaled in the descriptor.

The inet_server_URL_type information indicates the type of data provided by a server corresponding to a signaled Internet URL. The type of data provided by the corresponding server can be identified according to a value allocated to the inet_server_URL_type information. Referring to the figure, when the inet_server_URL_type information has a value of “0x01”, the inet_server_URL_type information can indicate a server which delivers SLS. When the inet_server_URL_type information has a value of “0x02”, the inet_server_URL_type information can indicate a server which provides an ESG (Electronic Service Guide). When the inet_server_URL_type information has a value of “0x03”, the inet_server_URL_type information can indicate a server which provides a template. When the inet_server_URL_type information has a value of “0x04”, the inet_server_URL_type information can indicate a server which provides all types of data. URL type which can be provided by one provider can be diversified by defining type of each URL as described above. In addition, the FIT size can be reduced by using one URL for the provider level in consideration of shortcomings of URL that the length is not restricted.

The inet_server_URL_length information indicates the URL length of a server.

The inet_server_URL information indicates the URL of a server.

FIG. 54 illustrates meaning of the capability_descriptor and values of the capability_category information according to an embodiment of the present invention.

The capability_descriptor according to the present embodiment may include descriptor_tag information, descriptor_length information, num_capability information, capability_category information, capability_code_type information, capability_code_int information, capability_code_string_length information and/or capability_code_string information.

The descriptor_tag information identifies the corresponding descriptor.

The descriptor_length information indicates the length of the descriptor.

The num_capability information indicates the number of signaled capabilities.

The capability_category information identifies capability category. In one embodiment, the capability_category information can indicate that capabilities for download protocols are signaled when the capability_category information is “0x01”, indicate that capabilities for an FEC algorithm are signaled when the capability_category information is “0x02”, indicate that capabilities for wrapper/archive formats are signaled when the capability_category information is “0x03”, indicate that capabilities for compression algorithms are signaled when the capability_category information is “0x04”, indicate that capabilities for media types are signaled when the capability_category information is “0x05” and indicate that capabilities for delivery protocols are signaled when the capability_category information is “0x06”.

The capability_code_type information indicates capability_code type.

The capability_code_int information indicates a capability code. The capability code can correspond to information indicating a degree of receiver capability.

The capability_code_string_length information indicates a string length of the capability code.

The capability_code_string information indicates a capability code.

The capability code can be defined in the form of an integer or a string according to the capability_code_int information or the capability_code_string information.

FIG. 55 illustrates a syntax of an FIT according to another embodiment of the present invention.

The FIT according to another embodiment of the present invention may include FIT_protocol_version information, broadcast_stream_id information, FIT_data_version information, FIT_length information, num_providers information, num_services information, service_id information, SLS_data_version information, service_category information, short_service_name_length information, short_service_name information, sp_indicator information, service_status information, SLS_simpleservice information, signaling_broadcast_flag information, IP_version_flag information, SLS_src_IP_addr_flag information, SLS_src_IP_addr information, SLS_dst_IP_addr information, SLS_dst_port_num information, SLS_TSI information, SLS_PLP_id information, num_service_level_descriptor information, a service_level_descriptor( ) element, num_provider_level_descriptor information, a provider_level_descriptor( ) element, num_FIT_level_descriptor information, an FIT_level_descriptor( ) element and/or a CRC( ) element.

The IP_version_flag information, SLS_src_IP_addr_flag information, SLS_src_IP_addr information, SLS_dst_IP_addr information, SLS_dst_port_num information, SLS_TSI information and/or SLS_PLP_id information can be defined as a signaling_broadcast_info( ) element.

The IP_version_flag information indicates the IP version used for the IP address delivered in the corresponding descriptor.

The SLS_src_IP_addr_flag information indicates whether the SLS_src_IP_addr information is present.

The SLS_src_IP_addr information indicates source IP address of packets which deliver SLS.

The SLS_dst_IP_addr information indicates destination IP address of packets which deliver SLS.

The SLS_dst_port_num information indicates destination port numbers of packets which deliver SLS.

The SLS_TSI information indicates a transport session through which SLS is delivered.

The SLS_PLP_id information identifies a location/region at which SLS is delivered. The SLS_PLP_id information identifies a PLP including the SLS. The SLS_PLP_id information may be included in link layer signaling and delivered.

Information or elements included in the FIT according to another embodiment of the present invention correspond to the aforementioned information or elements having the same names and thus description thereof is omitted.

According to the present embodiment, bootstrapping information about SLS can be signaled using a flag instead of a descriptor. In this case, the FIT size can be reduced.

FIG. 56 compares methods for signaling information about service level signaling delivered through a broadcast network according to an embodiment of the present invention.

The information included in the aforementioned signaling_broadcast_descriptor may be signaled through the FIT by being included in the aforementioned signaling_broadcast_info( ) element.

In this case, the descriptor_tag information and/or the descriptor_length information included in the signaling_broadcast_descriptor may be omitted, and thus up to 2 bytes from among bytes allocated for FIT signaling can be reduced.

FIG. 57 is a table showing descriptor type and locations at which descriptors can be included according to an embodiment of the present invention.

According to the present embodiment, a capability_descriptor can be included in a service level descriptor and a signaling_over_internet_descriptor can be included in a provider level descriptor.

Information that can be included in each descriptor has been described.

According to the present embodiment, the FIT may not separately include the signaling_broadcast_descriptor, and the signaling_broadcast_info( ) element can signal information necessary to bootstrap service level signaling.

FIG. 58 illustrates an FIT in XML format according to another embodiment of the present invention.

The FIT according to the present embodiment may include @protocol_version information, @Broadcast_stream_id information, @FIT_data_version information, a provider element, an inet_server_URL element, @type information, a service element, @service_id information, @SLS_data_version information, @service_category information, @service_name information, @sp_indicator information, @service_status information, @SLS_simpleservice information, a capability element, a signaling_broadcast element, a service_level_descriptor element, a signaling_on_inet_URL element, a provider_level_descriptor( ) element, an FIT_level_descriptor( ) element and/or a CRC( ) element.

The provider element includes information about a provider. The provider element can signal information about 0 to N providers.

The inet_server_URL element includes information indicating the URL of a server which provides data through the Internet.

The @type information indicates the type of data provided by the server having the URL identified by the inet_server_URL element. The @type information can identify a server delivering SLS, a server providing an ESG, a server providing a template and a server providing all types of data according to values thereof.

The capability element can include information contained in the aforementioned capability_descriptor.

The signaling_broadcast element can include information contained in the aforementioned signaling_broadcast_descriptor.

FIG. 59 illustrates description about information included in an FIT according to an embodiment of the present invention.

The FIT may include FIT_protocol_version information, broadcast_stream_id information, FIT_data_version information, FIT_length information, num_providers information, num_services information, service_id information, SLS_data_version information, service_category information, short_service_name_length information, short_service_name information, sp_indicator information, service_status information, SLS_simpleservice information, capability_flag information, signaling_broadcast_flag information, capability_code information, num_service_level_descriptor information, a service_level_descriptor( ) element, num_provider_level_descriptor information, a provider_level_descriptor( ) element, num_FIT_level_descriptor information, an FIT_level_descriptor( ) element and/or a CRC( ) element.

The SLS_simpleservice information can indicate whether a service is a simple broadcast service. The SLS_simpleservice information can indicate whether all components included in the service are delivered through a broadcast network or some components are delivered through a broadband network. That is, the SLS_simpleservice information indicates whether the receiver needs to access the broadband network in order to effectively present one or more broadcast services.

The num_provider_level_descriptor information indicates the number of provider level descriptors.

The provider_level_descriptor( ) element can include a provider level descriptor including description information about a provider.

The aforementioned information and/or elements have been described above.

FIG. 60 illustrates a signaling connecting structure in a procedure in which the receiver acquires a service according to an embodiment of the present invention.

In the present embodiment, service 1 (Srv1) and service 2 (Srv2) are delivered through a broadcast stream. SLS for each service is delivered through a broadcast network.

In this case, the receiver accesses a dedicated region in which an FIT is delivered in a broadcast signal to acquire the FIT and obtains the FIT_version information of the FIT. When the version of the FIT has been changed, the receiver parses the FIT.

The receiver acquires information about service 1 and service 2 in loops for service 1 and service 2 in the FIT. The information about the services is shown in the figure. Particularly, the information can include a signaling_broadcast_descriptor ( ) element. The signaling_broadcast_descriptor ( ) element can include the aforementioned signaling_broadcast_descriptor and the receiver can acquire SLS for service 1 and SLS for service 2 using information included in the signaling_broadcast_descriptor.

The receiver can acquire the SLS for each service and access a session delivering components included in service 1 and/or service 2 using the SLS information. The receiver acquires components for presenting the services from the corresponding session and present service 1 and/or service 2 viewers.

FIG. 61 illustrates a signaling connecting structure in a procedure in which the receiver acquires a service according to another embodiment of the present invention.

In the present embodiment, service 1 (Srv1) and service 2 (Srv2) are delivered through a broadcast stream. SLS for service 1 can be delivered through a broadcast network, whereas SLS for service 2 can be delivered through a broadband network.

In this case, the receiver acquires an FIT by accessing a dedicated region in which the FIT is delivered in a broadcast signal and obtains the FIT_version information of the FIT. When the version of the FIT has been changed, the receiver parses the FIT.

The receiver acquires information about service 1 and service 2 in loops for service 1 and service 2 in the FIT. The information about the services is shown in the figure. Particularly, the loop for service 1 can include a signaling_broadcast_descriptor ( ) element and the loop for service 2 can include a signaling_on_inet_URL_descriptor ( ) element.

The signaling_broadcast_descriptor ( ) element can include the aforementioned signaling_broadcast_descriptor and the receiver can acquire SLS for service 1 using information in the signaling_broadcast_descriptor.

The signaling_on_inet_URL_descriptor ( ) element can include the aforementioned signaling_on_inet_descriptor and the receiver can acquire SLS delivered through the broadband network using information in the signaling_on_inet_descriptor.

The receiver can access a session delivering components included in service 1 and/or service 2 using the acquired SLS information. The receiver acquires the components for presenting the services from the corresponding session and presents service 1 and/or service 2 to viewers.

FIG. 62 is a diagram showing a template delivery table of a table (or a fragment) for transmitting signaling information according to an embodiment of the present invention.

The table or the fragment for transmitting the signaling information described in the present invention may be defined in a template structure and a structure of the template may be pre-shared by a transmitting end and a receiving end.

When the XML form is used to transmit the signaling information described in the present invention, if the template is defined to change some signaling information, corresponding content may be updated. Accordingly, it is not required to change the entire signaling information and, thus, an unnecessary delivery band may be effectively reduced and it may not be necessary for a receiver to perform an unnecessary operation of updating even signaling information that is not required to be changed.

According to an embodiment of the present invention, the template delivery table may include a Table_id field, a Version_number field, a Table_length field, an encoding_type field, a Table_id_extension field, a current_segment_number field, a last_segment_number field, a Signaling_id field, a Signaling_version field, a Template_id field, a Template_version field, a template_length field, and/or a template field.

The Table_id field may be information for identifying a table.

The Version_number field may be information for identifying a version of a table.

The Table_length field may be information indicating a length of a table.

The encoding_type field may be information for identifying a type of encoding applied to the signaling table.

The Table_id_extension field may be extended information for the Table_id field. When the Table_id_extension field requires additional information to identify a table, the field may include information.

The current_segment_number field may be information indicating the number of a current segment for transmitting a signaling table.

The last_segment_number field may be information indicating the number of a last segment for transmitting a signaling table.

The Signaling_id field may be information for identifying signaling information.

The Signaling_version field may be information indicating a version of signaling information.

The Template_id field may be information for identifying a template.

The Template_version field may be information for identifying a version of a template.

The template_length field may be information indicating a length of a template.

The template field may include a template.

A transmitter may transmit the aforementioned template delivery table to a receiver and the receiver may update required signaling table/fragment/information by using the information and template included in the template delivery table.

FIG. 63 is a diagram illustrating FIT and a descriptor included therein according to an embodiment of the present invention.

According to an embodiment of the present invention, the FIT may include FIT_protocol_version information, Broadcast_stream_id information, FIT_data_version information, FIT_length information, num_services information, service_id information, provider_id information, service_category information, sp_indicator information, SLS_data_version information, service_status information, short_service_name_length information, short_service_name information, SLS_simpleservice information, num_service_level_descriptor information, service_level_descriptor( ) element, num_FIT_level_descriptor information, FIT_level_descriptor( ) element, and/or CRC( ) element.

The provider_id information may be information for identifying a provider for providing a service.

In the present embodiment, a description of the information and/or element included in the FIT may be replaced with information and/or element with the same term as in the aforementioned description and/or drawings.

According to an embodiment of the present invention, the FIT may include capability_descriptor, signaling_broadcast_descriptor, and/or signaling_on_internet_descriptor.

For example, the capability_descriptor and the signaling_broadcast_descriptor may be included in service_level_descriptor( ) element including descriptors for describing attribute of a service. The signaling_on_internet_descriptor may be included in service_level_descriptor( ) element and/or FIT_level_descriptor( ) element.

A description of the information and/or element included in the capability_descriptor, the signaling_broadcast_descriptor, and/or the signaling_on_internet_descriptor may be replaced with the above description.

FIG. 64 is a diagram illustrating FIT and a descriptor included therein according to an embodiment of the present invention.

The descriptor included in the FIT may be divided into several groups. In this case, a broadcast system may manage a version for each group and perform update and so on, thereby conserving resources.

According to an embodiment of the present invention, the FIT may include FIT_protocol_version information, Broadcast_stream_id information, group_id information, version information, num_services information, service_id information, provider_id information, service_category information, sp_indicator information, SLS_data_version information, service_status information, short_service_name_length information, short_service_name information, SLS_simpleservice information, num_service_level_descriptor information, service_level_descriptor( ) element, num_FIT_level_descriptor information, FIT_level_descriptor( ) element, and/or CRC( ) element.

The group_id information may be information for identifying a group of the descriptor included in the FIT.

According to the present invention, the FIT may include service_status_descriptor, service_name_descriptor, capability_descriptor, service_bootstrap_descriptor, signaling_template_descriptor, and/or signaling_over_internet_descriptor.

The service_status_descriptor may include SLS_data_version information and/or service status information.

The service_name_descriptor may include short_service_name_length information and/or short service name information.

The signaling_template_descriptor may include a partial or entire portion of information included in the aforementioned template delivery table.

A description of the capability_descriptor, service_bootstrap_descriptor and/or the signaling_over_internet_descriptor (or signaling_on_inet_descriptor) will be replaced with a descriptor with the same term as in the above description.

According to the present embodiment, when the group_id has a value ‘1’, the FIT may include service_status_descriptor and service_name_descriptor. When the group_id has a value ‘2’, the FIT may include service_status_descriptor, service_name_descriptor, capability_descriptor, and service_bootstrap_descriptor. When the group_id has a value ‘3’, the FIT may include service_status_descriptor, service_name_descriptor, capability_descriptor, service_bootstrap_descriptor, signaling_template_descriptor, and signaling_over_internet_descriptor.

According to the present embodiment, before parsing the entire portion of the FIT, the receiver may acquire group_id from the FIT and then determine whether the descriptor included in the FIT is added, deleted, or changed. When the descriptor included in the FIT is changed, the receiver may update a corresponding region/portion of the FIT.

FIG. 65 is a diagram illustrating a method of operatively connecting broadcast signaling and electronic service guide (ESG) according to an embodiment of the present invention.

According to the present invention, when signaling that is described above or below and ESG are operatively connected, service acquisition according to viewer selection may be more effectively performed.

The service_id described in the FIT may be unique in a broadcast stream or in a broadcast area. The ESG service fragment may correspond to a data unit including data for transmitting service guide. The globalServiceID included in the ESG service fragment and serviced included in the USD element may be defined in the form of URI. The globalServiceID and the serviced may be defined globally and uniquely or may be defined to be identical.

In this case, the service ID information (element) to be included in the FIT and service ID information to be included in the ESG and/or the USD and corresponding to the service ID information (element) may have the object of providing a connection relationship of FIT, ESG, USD, and announcement structure in a broadcast stream. Accordingly, the service ID in the broadcast stream needs to be uniquely maintained.

The drawing illustrates an ESG service fragment and a connection relationship between the USD and the FIT. The @globalServiceId (URI form) defined in the service fragment may be matched with the serviceId (URI form) of the USD and may be used as linkage for connection between the service fragment and the USD. The FITServiceId information to be included in the service fragment and the @atscServiceID information to be included in the USD may be matched with the Service ID information defined in the FIT and may connect the FIT and the service fragment or may be used as linkage for connecting the FIT and the USD.

To this end, the USD may define two service IDs. That is, the @serviceId for connecting the service fragment including one service guide and the signaling (e.g., service level signaling) described in the present invention and the @atscServiceID for connecting the SLS and the FIT (or SLT) with respect to the broadcast service described in the present invention may be included in the USD.

In addition, the FITServiceId information may be additionally defined in the service fragment of the ESG and a method of adding the FITServiceId information may include (1) a method of additionally defining FITServiceId information as attribute of the service fragment, (2) a method of extending and defining the FITServiceId information as child fragment of the service fragment, and (3) a method of extending and defining FITServiceId information to a child fragment in the PrivateExtension part of the service fragment.

FIG. 66 is a diagram showing a connection relationship between ESG service fragment and signaling of the present invention, according to an embodiment of the present invention.

In the ESG service fragment pre-defined in OMA BCAST, and so on, a service may be identified by the @globalServiceID information and, in the USBD/USD, a service may be identified by the serviceId information.

The @globalServiceID information of the ESG service fragment may be matched with a value of the @ServiceId information included in the USD of the SLS and the ESG service fragment may be connected to the USD of the SLS.

The Service ID information included in the FIT may be matched with a value of the FITServiceID information included in the ESG service fragment and the FIT and the ESG service fragment may be connected. The Service ID information included in the FIT may be matched with a value of the @atscServiceId information included in the USD and the FIT may be connected to the USD.

According to the present embodiment, upon acquiring FIT (or SLT) in a broadcast stream, a broadcast receiver may directly acquire ESG of a broadcast service by using the Service ID information included in the FIT (or SLT).

When the ESG service fragment is not directly defined in the FITServiceID or is not included in the FITServiceID, the receiver may search for USD including the @atscServiceID information matched with the Service ID information of the FIT (or SLT) and find ESG service fragment by using the @serviceId information included in the corresponding USD.

FIG. 67 is a view showing a protocol stack for a next generation broadcasting system according to an embodiment of the present invention.

The broadcasting system according to the present invention may correspond to a hybrid broadcasting system in which an Internet Protocol (IP) centric broadcast network and a broadband are coupled.

The broadcasting system according to the present invention may be designed to maintain compatibility with a conventional MPEG-2 based broadcasting system.

The broadcasting system according to the present invention may correspond to a hybrid broadcasting system based on coupling of an IP centric broadcast network, a broadband network, and/or a mobile communication network (or a cellular network).

Referring to the figure, a physical layer may use a physical protocol adopted in a broadcasting system, such as an ATSC system and/or a DVB system. For example, in the physical layer according to the present invention, a transmitter/receiver may transmit/receive a terrestrial broadcast signal and convert a transport frame including broadcast data into an appropriate form.

In an encapsulation layer, an IP datagram is acquired from information acquired from the physical layer or the acquired IP datagram is converted into a specific frame (for example, an RS Frame, GSE-lite, GSE, or a signal frame). The frame main include a set of IP datagrams. For example, in the encapsulation layer, the transmitter include data processed from the physical layer in a transport frame or the receiver extracts an MPEG-2 TS and an IP datagram from the transport frame acquired from the physical layer.

A fast information channel (FIC) includes information (for example, mapping information between a service ID and a frame) necessary to access a service and/or content. The FIC may be named a fast access channel (FAC).

The broadcasting system according to the present invention may use protocols, such as an Internet Protocol (IP), a User Datagram Protocol (UDP), a Transmission Control Protocol (TCP), an Asynchronous Layered Coding/Layered Coding Transport (ALC/LCT), a Rate Control Protocol/RTP Control Protocol (RCP/RTCP), a Hypertext Transfer Protocol (HTTP), and a File Delivery over Unidirectional Transport (FLUTE). A stack between these protocols may refer to the structure shown in the figure.

In the broadcasting system according to the present invention, data may be transported in the form of an ISO based media file format (ISOBMFF). An Electrical Service Guide (ESG), Non Real Time (NRT), Audio/Video (A/V), and/or general data may be transported in the form of the ISOBMFF.

Transport of data through a broadcast network may include transport of a linear content and/or transport of a non-linear content.

Transport of RTP/RTCP based A/V and data (closed caption, emergency alert message, etc.) may correspond to transport of a linear content.

An RTP payload may be transported in the form of an RTP/AV stream including a Network Abstraction Layer (NAL) and/or in a form encapsulated in an ISO based media file format. Transport of the RTP payload may correspond to transport of a linear content. Transport in the form encapsulated in the ISO based media file format may include an MPEG DASH media segment for A/V, etc.

Transport of a FLUTE based ESG, transport of non-timed data, transport of an NRT content may correspond to transport of a non-linear content. These may be transported in an MIME type file form and/or a form encapsulated in an ISO based media file format. Transport in the form encapsulated in the ISO based media file format may include an MPEG DASH media segment for A/V, etc.

Transport through a broadband network may be divided into transport of a content and transport of signaling data.

Transport of the content includes transport of a linear content (A/V and data (closed caption, emergency alert message, etc.)), transport of a non-linear content (ESG, non-timed data, etc.), and transport of a MPEG DASH based Media segment (A/V and data).

Transport of the signaling data may be transport including a signaling table (including an MPD of MPEG DASH) transported through a broadcasting network.

In the broadcasting system according to the present invention, synchronization between linear/non-linear contents transported through the broadcasting network or synchronization between a content transported through the broadcasting network and a content transported through the broadband may be supported. For example, in a case in which one UD content is separately and simultaneously transported through the broadcasting network and the broadband, the receiver may adjust the timeline dependent upon a transport protocol and synchronize the content through the broadcasting network and the content through the broadband to reconfigure the contents as one UD content.

An applications layer of the broadcasting system according to the present invention may realize technical characteristics, such as Interactivity, Personalization, Second Screen, and automatic content recognition (ACR). These characteristics are important in extension from ATSC 2.0 to ATSC 3.0. For example, HTML5 may be used for a characteristic of interactivity.

In a presentation layer of the broadcasting system according to the present invention, HTML and/or HTML5 may be used to identify spatial and temporal relationships between components or interactive applications.

In the present invention, signaling includes signaling information necessary to support effective acquisition of a content and/or a service. Signaling data may be expressed in a binary or XMK form. The signaling data may be transmitted through the terrestrial broadcasting network or the broadband.

A real-time broadcast A/V content and/or data may be expressed in an ISO Base Media File Format, etc. In this case, the A/V content and/or data may be transmitted through the terrestrial broadcasting network in real time and may be transmitted based on IP/UDP/FLUTE in non-real time. Alternatively, the broadcast A/V content and/or data may be received by receiving or requesting a content in a streaming mode using Dynamic Adaptive Streaming over HTTP (DASH) through the Internet in real time. In the broadcasting system according to the embodiment of the present invention, the received broadcast A/V content and/or data may be combined to provide various enhanced services, such as an Interactive service and a second screen service, to a viewer.

In a hybrid-based broadcast system of a TS and an IP stream, a link layer may be used to transmit data having a TS or IP stream type. When various types of data are to be transmitted through a physical layer, the link layer may convert the data into a format supported by the physical layer and deliver the converted data to the physical layer. In this way, the various types of data may be transmitted through the same physical layer. Here, the physical layer may correspond to a step of transmitting data using an MIMO/MISO scheme or the like by interleaving, multiplexing, and/or modulating the data.

The link layer needs to be designed such that an influence on an operation of the link layer is minimized even when a configuration of the physical layer is changed. In other words, the operation of the link layer needs to be configured such that the operation may be compatible with various physical layers.

The present invention proposes a link layer capable of independently operating irrespective of types of an upper layer and a lower layer. In this way, it is possible to support various upper layers and lower layers. Here, the upper layer may refer to a layer of a data stream such as a TS stream, an IP stream, or the like. Here, the lower layer may refer to the physical layer. In addition, the present invention proposes a link layer having a correctable structure in which a function supportable by the link layer may be extended/added/deleted. Moreover, the present invention proposes a scheme of including an overhead reduction function in the link layer such that radio resources may be efficiently used.

In this figure, protocols and layers such as IP, UDP, TCP, ALC/LCT, RCP/RTCP, HTTP, FLUTE, and the like are as described above.

In this figure, a link layer t88010 may be another example of the above-described data link (encapsulation) part. The present invention proposes a configuration and/or an operation of the link layer t88010. The link layer t88010 proposed by the present invention may process signaling necessary for operations of the link layer and/or the physical layer. In addition, the link layer t88010 proposed by the present invention may encapsulate TS and IP packets and the like, and perform overhead reduction in this process.

The link layer t88010 proposed by the present invention may be referred to by several terms such as data link layer, encapsulation layer, layer 2, and the like. According to a given embodiment, a new term may be applied to the link layer and used.

FIG. 68 is a conceptual diagram illustrating an interface of a link layer according to an embodiment of the present invention.

Referring to FIG. 68, the transmitter may consider an exemplary case in which IP packets and/or MPEG-2 TS packets mainly used in the digital broadcasting are used as input signals. The transmitter may also support a packet structure of a new protocol capable of being used in the next generation broadcast system. The encapsulated data of the link layer and signaling information may be transmitted to a physical layer. The transmitter may process the transmitted data (including signaling data) according to the protocol of a physical layer supported by the broadcast system, such that the transmitter may transmit a signal including the corresponding data.

On the other hand, the receiver may recover data and signaling information received from the physical layer into other data capable of being processed in a upper layer. The receiver may read a header of the packet, and may determine whether a packet received from the physical layer indicates signaling information (or signaling data) or recognition data (or content data).

The signaling information (i.e., signaling data) received from the link layer of the transmitter may include first signaling information that is received from an upper layer and needs to be transmitted to an upper layer of the receiver; second signaling information that is generated from the link layer and provides information regarding data processing in the link layer of the receiver; and/or third signaling information that is generated from the upper layer or the link layer and is transferred to quickly detect specific data (e.g., service, content, and/or signaling data) in a physical layer.

FIG. 69 illustrates an operation in a normal mode corresponding to one of operation modes of a link layer according to an embodiment of the present invention.

The link layer proposed by the present invention may have various operation modes for compatibility between an upper layer and a lower layer. The present invention proposes a normal mode and a transparent mode of the link layer. Both the operation modes may coexist in the link layer, and an operation mode to be used may be designated using signaling or a system parameter. According to a given embodiment, one of the two operation modes may be implemented. Different modes may be applied according to an IP layer, a TS layer, and the like input to the link layer. In addition, different modes may be applied for each stream of the IP layer and for each stream of the TS layer.

According to a given embodiment, a new operation mode may be added to the link layer. The new operation mode may be added based on configurations of the upper layer and the lower layer. The new operation mode may include different interfaces based on the configurations of the upper layer and the lower layer. Whether to use the new operation mode may be designated using signaling or a system parameter.

In the normal mode, data may be processed through all functions supported by the link layer, and then delivered to a physical layer.

First, each packet may be delivered to the link layer from an IP layer, an MPEG-2 TS layer, or another particular layer t89010. In other words, an IP packet may be delivered to the link layer from an IP layer. Similarly, an MPEG-2 TS packet may be delivered to the link layer from the MPEG-2 TS layer, and a particular packet may be delivered to the link layer from a particular protocol layer.

Each of the delivered packets may go through or not go through an overhead reduction process t89020, and then go through an encapsulation process t89030.

First, the IP packet may go through or not go through the overhead reduction process t89020, and then go through the encapsulation process t89030. Whether the overhead reduction process t89020 is performed may be designated by signaling or a system parameter. According to a given embodiment, the overhead reduction process t89020 may be performed or not performed for each IP stream. An encapsulated IP packet may be delivered to the physical layer.

Second, the MPEG-2 TS packet may go through the overhead reduction process t89020, and go through the encapsulation process t89030. The MPEG-2 TS packet may not be subjected to the overhead reduction process t89020 according to a given embodiment. However, in general, a TS packet has sync bytes (0x47) and the like at the front and thus it may be efficient to eliminate such fixed overhead. The encapsulated TS packet may be delivered to the physical layer.

Third, a packet other than the IP or TS packet may or may not go through the overhead reduction process t89020, and then go through the encapsulation process t89030. Whether or not the overhead reduction process t89020 is performed may be determined according to characteristics of the corresponding packet. Whether the overhead reduction process t89020 is performed may be designated by signaling or a system parameter. The encapsulated packet may be delivered to the physical layer.

In the overhead reduction process t89020, a size of an input packet may be reduced through an appropriate scheme. In the overhead reduction process t89020, particular information may be extracted from the input packet or generated. The particular information is information related to signaling, and may be transmitted through a signaling region. The signaling information enables a receiver to restore an original packet by restoring changes due to the overhead reduction process t89020. The signaling information may be delivered to a link layer signaling process t89050.

The link layer signaling process t89050 may transmit and manage the signaling information extracted/generated in the overhead reduction process t89020. The physical layer may have physically/logically divided transmission paths for signaling, and the link layer signaling process t89050 may deliver the signaling information to the physical layer according to the divided transmission paths. Here, the above-described FIC signaling process t89060, EAS signaling process t89070, or the like may be included in the divided transmission paths. Signaling information not transmitted through the divided transmission paths may be delivered to the physical layer through the encapsulation process t89030.

Signaling information managed by the link layer signaling process t89050 may include signaling information delivered from the upper layer, signaling information generated in the link layer, a system parameter, and the like. Specifically, the signaling information may include signaling information delivered from the upper layer to be subsequently delivered to an upper layer of the receiver, signaling information generated in the link layer to be used for an operation of a link layer of the receiver, signaling information generated in the upper layer or the link layer to be used for rapid detection in a physical layer of the receiver, and the like.

Data going through the encapsulation process t89030 and delivered to the physical layer may be transmitted through a data pipe (DP) t89040. Here, the DP may be a physical layer pipe (PLP). Signaling information delivered through the above-described divided transmission paths may be delivered through respective transmission paths. For example, an FIC signal may be transmitted through an FIC t89080 designated in a physical frame. In addition, an EAS signal may be transmitted through an EAC t89090 designated in a physical frame. Information about presence of a dedicated channel such as the FIC, the EAC, or the like may be transmitted to a preamble area of the physical layer through signaling, or signaled by scrambling a preamble using a particular scrambling sequence. According to a given embodiment, FIC signaling/EAS signaling information may be transmitted through a general DP area, PLS area, or preamble rather than a designated dedicated channel.

The receiver may receive data and signaling information through the physical layer. The receiver may restore the received data and signaling information into a form processable in the upper layer, and deliver the restored data and signaling information to the upper layer. This process may be performed in the link layer of the receiver. The receiver may verify whether a received packet is related to the signaling information or the data by reading a header of the packet and the like. In addition, when overhead reduction is performed at a transmitter, the receiver may restore a packet, overhead of which has been reduced through the overhead reduction process, to an original packet. In this process, the received signaling information may be used.

FIG. 70 illustrates an operation in a transparent mode corresponding to one of operation modes of a link layer according to an embodiment of the present invention.

In the transparent mode, data may not be subjected to functions supported by the link layer or may be subjected to some of the functions, and then delivered to a physical layer. In other words, in the transparent mode, a packet delivered to an upper layer may be delivered to a physical layer without going through a separate overhead reduction and/or encapsulation process. Other packets may go through the overhead reduction and/or encapsulation process as necessary. The transparent mode may be referred to as a bypass mode, and another term may be applied to the transparent mode.

According to a given embodiment, some packets may be processed in the normal mode and some packets may be processed in the transparent mode based on characteristics of the packets and a system operation.

A packet to which the transparent mode may be applied may be a packet having a type well known to a system. When the packet may be processed in the physical layer, the transparent mode may be used. For example, a well-known TS or IP packet may go through separate overhead reduction and input formatting processes in the physical layer and thus the transparent mode may be used in a link layer step. When the transparent mode is applied and a packet is processed through input formatting and the like in the physical layer, an operation such as the above-described TS header compression may be performed in the physical layer. On the other hand, when the normal mode is applied, a processed link layer packet may be treated as a GS packet and processed in the physical layer.

In the transparent mode, a link layer signaling module may be included when signal transmission needs to be supported. As described above, the link layer signaling module may transmit and manage signaling information. The signaling information may be encapsulated and transmitted through a DP, and FIC signaling information and EAS signaling information having divided transmission paths may be transmitted through an FIC and an EAC, respectively.

In the transparent mode, whether information corresponds to signaling information may be displayed using a fixed IP address and port number. In this case, the signaling information may be filtered to configure a link layer packet, and then transmitted through the physical layer.

FIG. 71 illustrates a configuration of a link layer at a transmitter according to an embodiment of the present invention (normal mode).

The present embodiment is an embodiment presuming that an IP packet is processed. The link layer at the transmitter may largely include a link layer signaling part for processing signaling information, an overhead reduction part, and/or an encapsulation part from a functional perspective. The link layer at the transmitter may further include a scheduler t91020 for a control of the entire operation of the link layer and scheduling, input and output parts of the link layer, and/or the like.

First, upper layer signaling information and/or system parameter t91010 may be delivered to the link layer. In addition, an IP stream including IP packets may be delivered to the link layer from an IP layer t91110.

As described above, the scheduler t91020 may determine and control operations of several modules included in the link layer. The delivered signaling information and/or system parameter t91010 may be filtered or used by the scheduler t91020. Information corresponding to a part of the delivered signaling information and/or system parameter t91010 and necessary for a receiver may be delivered to the link layer signaling part. In addition, information corresponding to a part of the signaling information and necessary for an operation of the link layer may be delivered to an overhead reduction control block t91120 or an encapsulation control block t91180.

The link layer signaling part may collect information to be transmitted as signaling in the physical layer, and transform/configure the information in a form suitable for transmission. The link layer signaling part may include a signaling manager t91030, a signaling formatter t91040, and/or a buffer for channels t91050.

The signaling manager t91030 may receive signaling information delivered from the scheduler t91020, signaling delivered from the overhead reduction part, and/or context information. The signaling manager t91030 may determine paths for transmission of the signaling information with respect to delivered data. The signaling information may be delivered through the paths determined by the signaling manager t91030. As described in the foregoing, signaling information to be transmitted through divided channels such as an FIC, an EAS, and the like may be delivered to the signaling formatter t91040, and other signaling information may be delivered to an encapsulation buffer t91070.

The signaling formatter t91040 may format associated signaling information in forms suitable for respective divided channels so that the signaling information may be transmitted through separately divided channels. As described in the foregoing, the physical layer may include physically/logically divided separate channels. The divided channels may be used to transmit FIC signaling information or EAS-related information. The FIC or EAS-related information may be divided by the signaling manager t91030 and input to the signaling formatter t91040. The signaling formatter t91040 may format information such that the information is suitable for respective separate channels. Besides the FIC and the EAS, when the physical layer is designed to transmit particular signaling information through separately divided channels, a signaling formatter for the particular signaling information may be added. Through this scheme, the link layer may be compatible with various physical layers.

The buffer for channels t91050 may deliver signaling information delivered from the signaling formatter t91040 to designated dedicated channels t91060. The number and content of the dedicated channels t91060 may vary depending on an embodiment.

As described in the foregoing, the signaling manager t91030 may deliver signaling information which is not delivered to a dedicated channel to the encapsulation buffer t91070. The encapsulation buffer t91070 may function as a buffer that receives the signaling information not delivered to the dedicated channel.

An encapsulation for signaling information t91080 may encapsulate the signaling information not delivered to the dedicated channel. A transmission buffer t91090 may function as a buffer that delivers the encapsulated signaling information to a DP for signaling information t91100. Here, the DP for signaling information t91100 may refer to the above-described PLS area.

The overhead reduction part may allow efficient transmission by eliminating overhead of packets delivered to the link layer. It is possible to configure overhead reduction parts, the number of which is the same as the number of IP streams input to the link layer.

An overhead reduction buffer t91130 may receive an IP packet delivered from an upper layer. The delivered IP packet may be input to the overhead reduction part through the overhead reduction buffer t91130.

An overhead reduction control block t91120 may determine whether to perform overhead reduction on a packet stream input to the overhead reduction buffer t91130. The overhead reduction control block t91120 may determine whether to perform overhead reduction for each packet stream. When overhead reduction is performed on the packet stream, packets may be delivered to an RoHC compressor t91140 and overhead reduction may be performed. When overhead reduction is not performed on the packet stream, packets may be delivered to the encapsulation part and encapsulation may be performed without overhead reduction. Whether to perform overhead reduction on packets may be determined by signaling information t91010 delivered to the link layer. The signaling information t91010 may be delivered to the encapsulation control block t91180 by the scheduler t91020.

The RoHC compressor t91140 may perform overhead reduction on a packet stream. The RoHC compressor t91140 may compress headers of packets. Various schemes may be used for overhead reduction. Overhead reduction may be performed by schemes proposed in the present invention. The present embodiment presumes an IP stream and thus the compressor is expressed as the RoHC compressor. However, the term may be changed according to a given embodiment. In addition, an operation is not restricted to compression of an IP stream, and overhead reduction may be performed on all types of packets by the RoHC compressor t91140.

A packet stream configuration block t91150 may divide IP packets having compressed headers into information to be transmitted to a signaling region and information to be transmitted to a packet stream. The information to be transmitted to the packet stream may refer to information to be transmitted to a DP area. The information to be transmitted to the signaling region may be delivered to a signaling and/or context control block t91160. The information to be transmitted to the packet stream may be transmitted to the encapsulation part.

The signaling and/or context control block t91160 may collect signaling and/or context information and deliver the collected information to the signaling manager t91030. In this way, the signaling and/or context information may be transmitted to the signaling region.

The encapsulation part may encapsulate packets in suitable forms such that the packets may be delivered to the physical layer. The number of configured encapsulation parts may be the same as the number of IP streams.

An encapsulation buffer t91170 may receive a packet stream for encapsulation. Packets subjected to overhead reduction may be received when overhead reduction is performed, and an input IP packet may be received without change when overhead reduction is not performed.

An encapsulation control block t91180 may determine whether to perform encapsulation on an input packet stream. When encapsulation is performed, the packet stream may be delivered to segmentation/concatenation t91190. When encapsulation is not performed, the packet stream may be delivered to a transmission buffer t91230. Whether to perform encapsulation of packets may be determined based on the signaling information t91010 delivered to the link layer. The signaling information t91010 may be delivered to the encapsulation control block t91180 by the scheduler t91020.

In the segmentation/concatenation t91190, the above-described segmentation or concatenation operation may be performed on packets. In other words, when an input IP packet is longer than a link layer packet corresponding to an output of the link layer, one IP packet may be divided into several segments to configure a plurality of link layer packet payloads. In addition, when the input IP packet is shorter than the link layer packet corresponding to the output of the link layer, several IP packets may be combined to configure one link layer packet payload.

A packet configuration table t91200 may have information about a configuration of segmented and/or concatenated link layer packets. A transmitter and a receiver may have the same information of the packet configuration table t91200. The transmitter and the receiver may refer to the information of the packet configuration table t91200. An index value of the information of the packet configuration table t91200 may be included in headers of the link layer packets.

A link layer header information block t91210 may collect header information generated in an encapsulation process. In addition, the link layer header information block t91210 may collect information included in the packet configuration table t91200. The link layer header information block t91210 may configure header information according to a header configuration of a link layer packet.

A header attachment block t91220 may add headers to payloads of the segmented and/or concatenated link layer packets. The transmission buffer t91230 may function as a buffer for delivering a link layer packet to a DP t91240 of the physical layer.

Each block or module and parts may be configured as one module/protocol or a plurality of modules/protocols in the link layer.

FIG. 72 illustrates a configuration of a link layer at a receiver according to an embodiment of the present invention (normal mode).

The present embodiment is an embodiment presuming that an IP packet is processed. The link layer at the receiver may largely include a link layer signaling part for processing signaling information, an overhead processing part, and/or a decapsulation part from a functional perspective. The link layer at the receiver may further include a scheduler for a control of the entire operation of the link layer and scheduling, input and output parts of the link layer, and/or the like.

First, information received through a physical layer may be delivered to the link layer. The link layer may process the information to restore the information to an original state in which the information is not yet processed by a transmitter, and deliver the information to an upper layer. In the present embodiment, the upper layer may be an IP layer.

Information delivered through dedicated channels t92030 separated from the physical layer may be delivered to the link layer signaling part. The link layer signaling part may distinguish signaling information received from the physical layer, and deliver the distinguished signaling information to each part of the link layer.

A buffer for channels t92040 may function as a buffer that receives signaling information transmitted through the dedicated channels. As described above, when physically/logically divided separate channels are present in the physical layer, it is possible to receive signaling information transmitted through the channels. When the information received from the separate channels is in a divided state, the divided information may be stored until the information is in a complete form.

A signaling decoder/parser t92050 may check a format of signaling information received through a dedicated channel, and extract information to be used in the link layer. When the signaling information received through the dedicated channel is encoded, decoding may be performed. In addition, according to a given embodiment, it is possible to check integrity of the signaling information.

A signaling manager t92060 may integrate signaling information received through several paths. Signaling information received through a DP for signaling t92070 to be described below may be integrated by the signaling manager t92060. The signaling manager t92060 may deliver signaling information necessary for each part in the link layer. For example, context information for recovery of a packet and the like may be delivered to the overhead processing part. In addition, signaling information for control may be delivered to a scheduler t92020.

General signaling information not received through a separate dedicated channel may be received through the DP for signaling t92070. Here, the DP for signaling may refer to a PLS or the like. A reception buffer t92080 may function as a buffer for receiving the signaling information received from the DP for signaling t92070. The received signaling information may be decapsulated in a decapsulation for signaling information block t92090. The decapsulated signaling information may be delivered to the signaling manager t92060 through a decapsulation buffer t92100. As described in the foregoing, the signaling manager t92060 may collect signaling information and deliver the collected signaling information to a desired part in the link layer.

The scheduler t92020 may determine and control operations of several modules included in the link layer. The scheduler t92020 may control each part of the link layer using receiver information t92010 and/or information delivered from the signaling manager t92060. In addition, the scheduler t92020 may determine an operation mode and the like of each part. Here, the receiver information t92010 may refer to information previously stored by the receiver. The scheduler t92020 may use information changed by a user such as a channel change and the like for control.

The decapsulation part may filter a packet received from a DP t92110 of the physical layer, and separate the packet based on a type of the packet. The number of configured decapsulation parts may be the same as the number of DPs that may be simultaneously decoded in the physical layer.

A decapsulation buffer t92120 may function as a buffer that receives a packet stream from the physical layer to perform decapsulation. A decapsulation control block t92130 may determine whether to decapsulate the received packet stream. When decapsulation is performed, the packet stream may be delivered to a link layer header parser t92140. When decapsulation is not performed, the packet stream may be delivered to an output buffer t92220. The signaling information delivered from the scheduler t92020 may be used to determine whether to perform decapsulation.

The link layer header parser t92140 may identify a header of a received link layer packet. When the header is identified, it is possible to identify a configuration of an IP packet included in a payload of the link layer packet. For example, the IP packet may be segmented or concatenated.

A packet configuration table t92150 may include payload information of link layer packets configured through segmentation and/or concatenation. The transmitter and the receiver may have the same information as information of the packet configuration table t92150. The transmitter and the receiver may refer to the information of the packet configuration table t92150. A value necessary for reassembly may be found based on index information included in the link layer packets.

A reassembly block t92160 may configure payloads of the link layer packets configured through segmentation and/or concatenation as packets of an original IP stream. The reassembly block t92160 may reconfigure one IP packet by collecting segments, or reconfigure a plurality of IP packet streams by separating concatenated packets. The reassembled IP packets may be delivered to the overhead processing part.

The overhead processing part may perform a reverse process of overhead reduction performed by the transmitter. In the reverse process, an operation of returning packets experiencing overhead reduction to original packets is performed. This operation may be referred to as overhead processing. The number of configured overhead processing parts may be the same as the number of DPs that may be simultaneously decoded in the physical layer.

A packet recovery buffer t92170 may function as a buffer that receives an RoHC packet or an IP packet decapsulated for overhead processing.

An overhead control block t92180 may determine whether to perform packet recovery and/or decompression of decapsulated packets. When the packet recovery and/or decompression are performed, the packets may be delivered to a packet stream recovery t92190. When the packet recovery and/or decompression are not performed, the packets may be delivered to the output buffer t92220. Whether to perform the packet recovery and/or decompression may be determined based on the signaling information delivered by the scheduler t92020.

The packet stream recovery t92190 may perform an operation of integrating a packet stream separated from the transmitter and context information of the packet stream. The operation may correspond to a process of restoring the packet stream such that the packet stream may be processed by an RoHC decompressor t92210. In this process, signaling information and/or context information may be delivered from a signaling and/or context control block t92200. The signaling and/or context control block t92200 may distinguish signaling information delivered from the transmitter and deliver the signaling information to the packet stream recovery t92190 such that the signaling information may be mapped to a stream suitable for a context ID.

The RoHC decompressor t92210 may recover headers of packets of a packet stream. When the headers are recovered, the packets of the packet stream may be restored to original IP packets. In other words, the RoHC decompressor t92210 may perform overhead processing.

The output buffer t92220 may function as a buffer before delivering an output stream to an IP layer t92230.

The link layer of the transmitter and the receiver proposed in the present invention may include the blocks or modules described above. In this way, the link layer may independently operate irrespective of the upper layer and the lower layer, and efficiently perform overhead reduction. In addition, a function which is supportable depending on the upper and lower layers may be easily extended/added/deleted.

FIG. 73 is a diagram illustrating definition according to link layer organization type according to an embodiment of the present invention.

When a link layer is actually embodied as a protocol layer, a broadcast service can be transmitted and received through one frequency slot. Here, an example of one frequency slot may be a broadcast channel that mainly has a specific bandwidth. As described above, according to the present invention, in a broadcast system in which a configuration of a physical layer is changed or in a plurality of broadcast systems with different physical layer configurations, a compatible link layer may be defined.

The physical layer may have a logical data path for an interface of a link layer. The link layer may access the logical data path of the physical layer and transmit information associated with the corresponding data path to the logical data path. The following types may be considered as the data path of the physical layer interfaced with the link layer.

In a broadcast system, a normal data pipe (Normal DP) may exist as a type of data path. The normal data pipe may be a data pipe for transmission of normal data and may include one or more data pipes according to a configuration of a physical layer.

In a broadcast system, a base data pipe (Base DP) may exist as a type of data path. The base data pipe may be a data pipe used for specific purpose and may transmit signaling information (entire or partial signaling information described in the present invention) and/or common data in a corresponding frequency slot. As necessary, in order to effectively manage a bandwidth, data that is generally transmitted through a normal data pipe may be transmitted through a base data pipe. When the amount of information to be transmitted when a dedicated channel is present exceeds processing capacity of a corresponding channel, the base data pipe may perform a complementary function. That is, data that exceeds the processing capacity of the corresponding channel may be transmitted through the base data pipe.

In general, the base data pipe continuously uses one designated data pipe. However, one or more data pipes may be dynamically selected for the base data pipe among a plurality of data pipes using a method such as physical layer signaling, link layer signaling, or the like in order to effectively manage a data pipe.

In a broadcast system, a dedicated channel may exist as a type of data path. The dedicated channel may be a channel used for signaling in a physical layer or a similar specific purpose and may include a fast information channel (FIC) for rapidly acquiring matters that are mainly served on a current frequency slot and/or an emergency alert channel (EAC) for immediately transmitting notification of emergency alert to a user.

In general, a logical data path is embodied in a physical layer in order to transmit the normal data pipe. A logical data path for the base data pipe and/or the dedicated channel may not be embodied in a physical layer.

A configuration of data to be transmitted in the link layer may be defined as illustrated in the drawing.

Organization Type 1 may refer to the case in which a logical data path includes only a normal data pipe.

Organization Type 2 may refer to the case in which a logical data path includes a normal data pipe and a base data pipe.

Organization Type 3 may refer to the case in which a logical data path includes a normal data pipe and a dedicated channel.

Organization Type 4 may refer to the case in which a logical data path includes a normal data pipe, a data base pipe, and a dedicated channel.

As necessary, the logical data path may include a base data pipe and/or a dedicated channel.

According to an embodiment of the present invention, a transmission procedure of signaling information may be determined according to configuration of a logical data path. Detailed information of signaling transmitted through a specific logical data path may be determined according to a protocol of an upper layer of a link layer defined in the present invention. Regarding a procedure described in the present invention, signaling information parsed through a upper layer may also be used and corresponding signaling may be transmitted in the form of an IP packet from the upper layer and transmitted again after being encapsulated in the form of a link layer packet.

When such signaling information is transmitted, a receiver may extract detailed signaling information from session information included in an IP packet stream according to protocol configuration. When signaling information of a upper layer is used, a database (DB) may be used or a shared memory may be used. For example, in the case of extracting the signaling information from the session information included in the IP packet stream, the extracted signaling information may be stored in a DB, a buffer, and/or a shared memory of the receiver. Then, when the signaling information is needed in a procedure of processing data in a broadcast signal, the signaling information may be obtained from the above storage device.

FIG. 74 is a diagram illustrating processing of a broadcast signal when a logical data path includes only a normal data pipe according to an embodiment of the present invention.

The diagram illustrates a structure of a link layer when the logical of the physical layer includes only a normal data pipe. As described above, the link layer may include a link layer signaling processor, an overhead reduction processor, and an encapsulation (decapsulation) processor. Transmission of information output from each functional module (which may be embodied as hardware or software) to an appropriate data path of the physical layer may be one of main functions of the link layer.

With regard to an IP stream configured on an upper layer of a link layer, a plurality of packet streams may be transmitted according to a data rate at which data is to be transmitted, and overhead reduction and encapsulation procedures may be performed for each respective corresponding packet stream. A physical layer may include a data pipe (DP) as a plurality of logical data paths that a link layer can access in one frequency band and may transmit a packet stream processed in a link layer for each respective packet stream. When the number of DPs is lower than that of packet streams to be transmitted, some of the packet streams may be multiplexed and input to a DP in consideration of a data rate.

The signaling processor may check transmission system information, related parameters, and/or signaling transmitted in a upper layer and collect information to be transmitted via signaling. Since only a normal data pipe is configured in a physical layer, corresponding signaling needs to be transmitted in the form of packet. Accordingly, signaling may be indicated using a header, etc. of a packet during link layer packet configuration. In this case, a header of a packet including signaling may include information for identifying whether signaling data is contained in a payload of the packet.

In the case of service signaling transmitted in the form of IP packet in a upper layer, in general, it is possible to process different IP packets in the same way. However, information of the corresponding IP packet can be read for a configuration of link layer signaling. To this end, a packet including signaling may be found using a filtering method of an IP address. For example, since IANA designates an IP address of 224.0.23.60 as ATSC service signaling, the receiver may check an IP packet having the corresponding IP address use the IP packet for configuration of link layer signaling. In this case, the corresponding packet needs to also be transmitted to a receiver, processing for the IP packet is performed without change. The receiver may parse an IP packet transmitted to a predetermined IP address and acquire data for signaling in a link layer.

When a plurality of broadcast services are transmitted through one frequency band, the receiver does not have to decode all DPs, and it is efficient to pre-check signaling information and to decode only a DP associated with a required service. Accordingly, with regard to an operation for a link layer of the receiver, the following procedures may be performed.

When a user selects or changes a service to be received, the receiver tunes a corresponding frequency and reads information of the receiver, stored in a DB, etc. with regard to a corresponding channel.

The receiver checks information about a DP that transmits link layer signaling and decodes the corresponding DP to acquire a link layer signaling packet.

The receiver parses the link layer signaling packet and acquires information about a DP that transmits data associated with a service selected by the user among one or more DPs transmitted through a current channel and overhead reduction information about a packet stream of the corresponding DP. The receiver may acquire information for identification of a DP that transmits the data associated with the service selected by the user from a link layer signaling packet and obtain a corresponding DP based on the information. In addition, the link layer signaling packet may include information indicating overhead reduction applied to the corresponding DP, and the receiver may restore a DP to which overhead reduction is applied, using the information.

The receiver transmits DP information to be received, to a physical layer processor that processes a signal or data in a physical layer and receives a packet stream from a corresponding DP.

The receiver performs encapsulation and header recovery on the packet stream decoded by the physical layer processor.

Then the receiver performs processing according to a protocol of a upper layer and provides a broadcast service to the user.

FIG. 75 is a diagram illustrating processing of a broadcast signal when a logical data path includes a normal data pipe and a base data pipe according to an embodiment of the present invention.

The diagram illustrates a structure of a link layer when the logical data path of the physical layer includes a base data pipe and a normal data pipe. As described above, the link layer may include a link layer signaling part, an overhead reduction part, and an encapsulation (decapsulation) part. In this case, a link layer processor for processing a signal and/or data in a link layer may include a link layer signaling processor, an overhead reduction processor, and an encapsulation (decapsulation) processor.

Transmission of information output from each functional module (which may be embodied as hardware or software) to an appropriate data path of the physical layer may be one of main functions of the link layer.

With regard to an IP stream configured on an upper layer of a link layer, a plurality of packet streams may be transmitted according to a data rate at which data is to be transmitted, and overhead reduction and encapsulation procedures may be performed for each respective corresponding packet stream.

A physical layer may include a data pipe (DP) as a plurality of logical data paths that a link layer can access in one frequency band and may transmit a packet stream processed in a link layer for each respective packet stream. When the number of DPs is lower than that of packet streams to be transmitted, some of the packet streams may be multiplexed and input to a DP in consideration of a data rate.

The signaling processor may check transmission system information, related parameters, upper layer signaling, etc. and collect information to be transmitted via signaling. Since a broadcast signal of the physical layer includes a base DP and a normal DP, signaling may be transmitted to the base DP and signaling data may be transmitted in the form of packet appropriate for transmission of the base DP in consideration of a data rate. In this case, signaling may be indicated using a header, etc. of a packet during link layer packet configuration. For example, a header of a link layer packet may include information indicating that data contained in a payload of the packet is signaling data.

In a physical layer structure in which a logical data path such as a base DP exists, it may be efficient to transmit data that is not audio/video content, such as signaling information to the base DP in consideration of a data rate. Accordingly, service signaling that is transmitted in the form of IP packet in a upper layer may be transmitted to the base DP using a method such as IP address filtering, etc. For example, IANA designates an IP address of 224.0.23.60 as ATSC service signaling, an IP packet stream with the corresponding IP address may be transmitted to the base DP.

When a plurality of IP packet streams about corresponding service signaling is present, the IP packet streams may be transmitted to one base DP using a method such as multiplexing, etc. However, a packet about different service signaling may be divided into field values such as a source address and/or a port. In this case, information required for configuration of link layer signaling can also be read from the corresponding service signaling packet.

When a plurality of broadcast services are transmitted through one frequency band, the receiver may not have to decode all DPs, may pre-check signaling information, and may decode only a DP that transmits data and/or a signal about a corresponding service. Accordingly, the receiver may perform the following operation with regard to data and/or processing in a link layer.

When a user selects or changes a service to be received, the receiver tunes a corresponding frequency and reads information of the receiver, stored in a DB, etc. with regard to a corresponding channel. Here, the information stored in the DB, etc. may include information for identification of the base DP.

The receiver decodes the base DP and acquires a link layer signaling packet included in the base DP.

The receiver parses the link layer signaling packet to acquire DP information for reception of the service selected by the user and overhead reduction information about a packet stream of the corresponding DP among a plurality of DPs transmitted through a current channel and overhead reduction information about a packet stream of the corresponding DP. The link layer signaling packet may include information for identification of a DP that transmits a signal and/or data associated with a specific service, and/or information for identification of a type of overhead reduction applied to a packet stream transmitted to the corresponding DP. The receiver may access one or more DPs or restore the packet included in the corresponding DP using the above information.

The receiver is a physical layer processor that processes a signal and/or data according to a protocol of a physical layer, transmits information about a DP to be received for a corresponding service, and receives a packet stream from the corresponding DP.

The receiver performs decapsulation and header recovery on the packet stream decoded in the physical layer and transmits the packet stream to a upper layer of the receiver in the form of IP packet stream.

Then, the receiver performs processing according to a upper layer protocol and provides a broadcast service to the user.

In the above-described process of acquiring the link layer packet by decoding the base DP, information about the base DP (e.g., an identifier (ID) information of the base DP, location information of the base DP, or signaling information included in the base DP) may be acquired during previous channel scan and then stored in a DB and the receiver may use the stored base DP. Alternatively, the receiver may acquire the base DP by first seeking a DP that the receiver has pre-accessed.

In the above-described process of acquiring the DP information for a service selected by the user and the overhead reduction information about a DP packet stream transmitting the corresponding service, by parsing the link layer packet, if the information about the DP transmitting the service selected by the user is transmitted through upper layer signaling (e.g., a layer higher than a link layer, or an IP layer), the receiver may acquire corresponding information from the DB, the buffer, and/or the shared memory as described above and use the acquired information as information about a DP requiring decoding.

If link layer signaling (link layer signaling information) and normal data (e.g., broadcast content data) is transmitted through the same DP or if only a DP of one type is used in a broadcast system, the normal data transmitted through the DP may be temporarily stored in the buffer or the memory while the signaling information is decoded and parsed. Upon acquiring the signaling information, the receiver may transmit a command for extracting a DP that should be obtained according to the corresponding signaling information to a device for extracting and processing the DP by a method using interior command words of the system.

FIG. 76 is a diagram illustrating processing of a broadcast signal when a logical data path includes a normal data pipe and a dedicated channel according to an embodiment of the present invention.

The diagram illustrates a structure of a link layer when the logical data path of the physical layer includes a dedicated channel and a normal data pipe. As described above, the link layer may include a link layer signaling part, an overhead reduction part, and an encapsulation (decapsulation) part. In this regard, a link layer processor to be included in the receiver may include a link layer signaling processor, an overhead reduction processor, and/or an encapsulation (decapsulation) processor. Transmission of information output from each functional module (which may be embodied as hardware or software) to an appropriate data path of the physical layer may be one of main functions of the link layer.

With regard to an IP stream configured on a upper layer of a link layer, a plurality of packet streams may be transmitted according to a data rate at which data is to be transmitted, and overhead reduction and encapsulation procedures may be performed for each respective corresponding packet stream. A physical layer may include a data pipe (DP) as a plurality of logical data paths that a link layer can access in one frequency band and may transmit a packet stream processed in a link layer for each respective packet stream. When the number of DPs is lower than that of packet streams to be transmitted, some of the packet streams may be multiplexed and input to a DP in consideration of a data rate.

The signaling processor may check transmission system information, related parameters, upper layer signaling, etc. and collect information to be transmitted via signaling. In a physical layer structure in which a logical data path such as a dedicate channel exists, it may be efficient to mainly transmit signaling information through a dedicated channel in consideration of a data rate. However, when a large amount of data needs to be transmitted through a dedicated channel, a bandwidth for the dedicated channel corresponding to the amount of the dedicated channel needs to be occupied, and thus it is general to set a high data rate of the dedicated channel. In addition, since a dedicated channel is generally received and decoded at higher speed than a DP, it is more efficient to signaling data in terms of information that needs to be rapidly acquired from the receiver. As necessary, when sufficient signaling data cannot be transmitted through the dedicated channel, signaling data such as the aforementioned link layer signaling packet may be transmitted through the normal DP, and signaling data transmitted through the dedicated channel may include information for identification of the corresponding link layer signaling packet.

A plurality of dedicated channels may exist as necessary and a channel may be enable/disable according to a physical layer.

In the case of service signaling transmitted in the form of IP packet in a upper layer, in general, it is possible to process different IP packets in the same way. However, information of the corresponding IP packet can be read for a configuration of link layer signaling. To this end, a packet including signaling may be found using a filtering method of an IP address. For example, since IANA designates an IP address of 224.0.23.60 as ATSC service signaling, the receiver may check an IP packet having the corresponding IP address use the IP packet for configuration of link layer signaling. In this case, the corresponding packet needs to also be transmitted to a receiver, processing for the IP packet is performed without change.

When a plurality of IP packet streams about service signaling is present, the IP packet streams may be transmitted to one DP together with audio/video data using a method such as multiplexing, etc. However, a packet about service signaling and audio/video data may be divided into field values of an IP address, a port, etc.

When a plurality of broadcast services are transmitted through one frequency band, the receiver does not have to decode all DPs, and it is efficient to pre-check signaling information and to decode only a DP that transmit signal and/or data associated with a required service. Thus, the receiver may perform processing according to a protocol of a link layer as the following procedure.

When a user selects or changes a service to be received, the receiver tunes a corresponding frequency and reads information stored in a DB, etc. with regard to a corresponding channel. The information stored in the DB may include information for identification of a dedicated channel and/or signaling information for acquisition of channel/service/program.

The receiver decodes data transmitted through the dedicated channel and performs processing associated with signaling appropriate for purpose of the corresponding channel. For example, a dedicated channel for transmission of FIC may store and update information such as a service and/or a channel, and a dedicated channel for transmission of EAC may transmit emergency alert information.

The receiver may acquire information of DP to be decoded using information transmitted to the dedicated channel. As necessary, when link layer signaling is transmitted through a DP, the receiver may pre-decode a DP that transmits signaling and transmit the DP to a dedicated channel in order to pre-acquire signaling information. In addition, a packet for link layer signaling may be transmitted through a normal DP, and in this case, the signaling data transmitted through the dedicated channel may include information for identification of a DP including a packet for link layer signaling.

The receiver acquires DP information for reception of a service selected by a user among a plurality of DPs that are transmitted to a current channel and overhead reduction information about a packet stream of the corresponding DP using the link layer signaling information. The link layer signaling information may include information for identification of a DP for transmission of a signal and/or data associated with a specific service, and/or information for identification of a type of overhead reduction applied to a packet stream transmitted to the corresponding DP. The receiver may access one or more DPs for a specific service or restore a packet included in the corresponding DP using the information.

The receiver transmits information for identification of a DP to be received by a physical layer to a physical layer processor that processes a signal and/or data in a physical layer and receives a packet stream from the corresponding DP.

The receiver performs decapsulation and header recovery on a packet stream decoded in a physical layer and transmits the packet stream to a upper layer of the receiver in the form of IP packet stream.

Then the receiver performs processing according to a protocol of a upper layer and provides a broadcast service to the user.

FIG. 77 is a diagram illustrating processing of a broadcast signal when a logical data path includes a normal data pipe, a base data pipe, and a dedicated channel according to an embodiment of the present invention.

The diagram illustrates a structure of a link layer when the logical data path of the physical layer includes a dedicated channel, a base data pipe, and a normal data pipe. As described above, the link layer may include a link layer signaling part, an overhead reduction part, and an encapsulation (decapsulation) part. In this regard, a link layer processor to be included in the receiver may include a link layer signaling processor, an overhead reduction processor, and/or an encapsulation (decapsulation) processor. Transmission of information output from each functional module (which may be embodied as hardware or software) to an appropriate data path of the physical layer may be one of main functions of the link layer.

With regard to an IP stream configured on a upper layer of a link layer, a plurality of packet streams may be transmitted according to a data rate at which data is to be transmitted, and overhead reduction and encapsulation procedures may be performed for each respective corresponding packet stream. A physical layer may include a data pipe (DP) as a plurality of logical data paths that a link layer can access in one frequency band and may transmit a packet stream processed in a link layer for each respective packet stream. When the number of DPs is lower than that of packet streams to be transmitted, some of the packet streams may be multiplexed and input to a DP in consideration of a data rate.

The signaling processor may check transmission system information, related parameters, upper layer signaling, etc. and collect information to be transmitted via signaling. Since a signal of the physical layer includes a base DP and a normal DP, it may be efficient to transmit signaling to the base DP in consideration of a data rate. In this case, the signaling data needs to be transmitted in the form of packet appropriate for transmission through the base DP. Signaling may be indicated using a header, etc. of a packet during link layer packet configuration. That is, a header of a link layer signaling packet including signaling data may include information indicating that signaling data is contained in a payload of the corresponding packet.

In a physical layer structure in which a dedicate channel and a base DP exist simultaneously, signaling information may be divided and transmitted to the dedicated channel and the base DP. In general, since a high data rate of the dedicated channel is not set, signaling information that has a small amount of signaling and needs to be rapidly acquired may be transmitted to the dedicated channel and signaling with a high amount of signaling to the base DP. As necessary, a plurality of dedicated channels may exist and a channel may be enable/disable according to a physical layer. In addition, the base DP may be configured with a separate structure from a normal DP. In addition, it is possible to designate one of normal DPs and use the normal DP as a base DP.

Service signaling that is transmitted in the form of IP packet in a upper layer may be transmitted to the base DP using a method such as IP address filtering, etc. An IP packet stream with a specific IP address and including signaling information may be transmitted to the base DP. When a plurality of IP packet streams about corresponding service signaling is present, the IP packet streams may be transmitted to one base DP using a method such as multiplexing, etc. A packet about different service signaling may be divided into field values such as a source address and/or a port. The receiver may read information required for configuration of the link layer signaling in the corresponding service signaling packet.

When a plurality of broadcast services are transmitted through one frequency band, the receiver may not have to decode all DPs, and it may be efficient to pre-check the signaling information and to decode only a DP that transmits a signal and/or data associated with a required service. Thus, the receiver may perform the following processors as processing according to a protocol of a link layer.

When a user selects or changes a service to be received, the receiver tunes a corresponding frequency and reads information stored in a database DB, etc. with regard to a corresponding channel. The information stored in the DB may include information for identification of a dedicated channel, information for identification of a base data pipe, and/or signaling information for acquisition of channel/service/program.

The receiver decodes data transmitted through the dedicated channel and performs processing associated with signaling appropriate for purpose of the corresponding channel. For example, a dedicated channel for transmission of FIC may store and update information such as a service and/or a channel, and a dedicated channel for transmission of EAC may transmit emergency alert information.

The receiver may acquire information of the base DP using information transmitted to the dedicated channel. The information transmitted to the dedicated channel may include information for identification of the base DP (e.g., an identifier of the base DP and/or an IP address of the base DP). As necessary, the receiver may update signaling information pre-stored in a DB of the receiver and related parameters to information transmitted in the dedicated channel.

The receiver may decode the base DP and acquire a link layer signaling packet. As necessary, the link layer signaling packet may be combined with signaling information received from the dedicated channel. The receiver may find the base DP using the dedicate channel and the signaling information pre-stored in the receiver.

The receiver acquires DP information for reception of a service selected by a user among a plurality of DPs that are transmitted to a current channel and overhead reduction information about a packet stream of the corresponding DP using the link layer signaling information. The link layer signaling information may include information for identification of a DP for transmission of a signal and/or data associated with a specific service, and/or information for identification of a type of overhead reduction applied to a packet stream transmitted to the corresponding DP. The receiver may access one or more DPs for a specific service or restore a packet included in the corresponding DP using the information.

The receiver transmits information for identification of a DP to be received by a physical layer to a physical layer processor that processes a signal and/or data in a physical layer and receives a packet stream from the corresponding DP.

The receiver performs decapsulation and header recovery on a packet stream decoded in a physical layer and transmits the packet stream to a upper layer of the receiver in the form of IP packet stream.

Then the receiver performs processing according to a protocol of a upper layer and provides a broadcast service to the user.

According to an embodiment of the present invention, when information for service signaling is transmitted by one or more IP packet streams, the IP packet streams may be multiplexed and transmitted as one base DP. The receiver may distinguish between packets for different service signaling through a field of a source address and/or a port. The receiver may read out information for acquiring/configuring link layer signaling from a service signaling packet.

In the process of processing signaling information transmitted through the dedicated channel, the receiver may obtain version information of the dedicated channel or information identifying whether update has been performed and, if it is judged that there is no change in the signaling information in the dedicated channel, the receiver may omit processing (decoding or parsing) of the signaling information transmitted through the dedicated channel. If it is confirmed that the dedicated channel has not been updated, the receiver may acquire information of a base DP using prestored information.

In the above-described process of acquiring the DP information for a service selected by the user and the overhead reduction information about the DP packet stream transmitting the corresponding service, if the information about the DP transmitting the service selected by the user is transmitted through upper layer signaling (e.g., a layer higher than a link layer, or an IP layer), the receiver may acquire the corresponding information from the DB, the buffer, and/or the shared memory as described above and use the acquired information as information about a DP requiring decoding.

If link layer signaling (link layer signaling information) and normal data (e.g., broadcast content data) is transmitted through the same DP or if only type of DP is used in a broadcast system, the normal data transmitted through the DP may be temporarily stored in the buffer or the memory while the signaling information is decoded and parsed. Upon acquiring the signaling information, the receiver may transmit a command for extracting a DP that should be obtained according to the corresponding signaling information to a device for extracting and processing the DP by a method using system interior command words.

FIG. 78 is a diagram illustrating a detailed processing operation of a signal and/or data in a link layer of a receiver when a logical data path includes a normal data pipe, a base data pipe, and a dedicated channel according to an embodiment of the present invention.

The present embodiment considers a situation in which one or more services provided by one or more broadcasters are transmitted in one frequency band. It may be considered that one broadcaster transmits one or more broadcast services, one service includes one or more components and a user receives content in units of broadcast services. In addition, some of one or more components included in one broadcast service may be replaced with other components according to user selection.

A fast information channel (FIC) and/or emergency alert channel (EAC) may be transmitted to a dedicated channel. A base DP and a normal DP may be differentiated in a broadcast signal and transmitted or managed. Configuration information of the FIC and/or the EAC may be transmitted through physical layer signaling so as to notify the receiver of the FIC and/or the EAC, and the link layer may format signaling according to the characteristic of the corresponding channel. Transmission of data to a specific channel of a physical layer is performed from a logical point of view and an actual operation may be performed according to the characteristic of a physical layer.

Information about a service of each broadcaster, transmitted in a corresponding frequency, and information about a path for reception of the service may be transmitted through the FIC. To this end, the following information may be provided (signaled) via link layer signaling.

System Parameter: Transmitter related parameter, and/or parameter related to a broadcaster that provides a service in a corresponding channel.

Link layer: which includes context information associated with IP header compression and/or ID of a DP to which corresponding context is applied.

Upper layer: IP address and/or UDP port number, service and/or component information, emergency alert information, and mapping relation information between a DP and an IP address of a packet stream transmitted in an IP layer.

When a plurality of broadcast services is transmitted through one frequency band, a receiver may not have to decode all DPs, and it may be efficient to pre-check signaling information and to decode only a DP about a required service. In a broadcast system, a transmitter may transmit information for identification of only a required DP through an FIC, and the receiver may check a DP to be accessed for a specific serviced, using the FIC. In this case, an operation associated with the link layer of the receiver may be performed as follows.

When a user selects or changes a service to be received by a user, the receiver tunes a corresponding frequency and reads information of a receiver, stored in a DB, etc. in regard to a corresponding channel. The information stored in the DB of the receiver may be configured by acquiring an FIC during initial channel scan and using information included in the FIC.

The receiver may receive an FIC and update a pre-stored DB or acquire information about a component about a service selected by the user and information about a mapping relation for DPs that transmit components from the FIC. In addition, the information about a base DP that transmits signaling may be acquired from the FIC.

When initialization information related to robust header compression (RoHC) is present in signaling transmitted through the FIC, the receiver may acquire the initialization information and prepare header recovery.

The receiver decodes a base DP and/or a DP that transmits a service selected by a user based on information transmitted through the FIC.

The receiver acquires overhead reduction information about a DP that is being received, included in the base DP, performs decapsulation and/or header recovery on a packet stream received in a normal DP using the acquired overhead information, and transmits the packet stream to a upper layer of the receiver in the form of IP packet stream.

The receiver may receive service signaling transmitted in the form of IP packet with a specific address through a base DP and transmit the packet stream to the upper layer with regard to a received service.

When emergency alert occurs, in order to rapidly transmit an emergency alert message to a user, the receiver receives signaling information included in a CAP message through signaling, parses the signaling information, and immediately transmits the signaling information to a user, and finds a path for reception of a corresponding service and receives service data when information of a path through which an audio/video service can be received via signaling can be confirmed. In addition, when information transmitted through a broadband and so on is present, an NRT service and additional information are received using corresponding uniform resource identifier (URI) information and so on. Signaling information associated with emergency alert will be described below in detail.

The receiver processes the emergency alert as follows.

The receiver recognizes a situation in which an emergency alert message is transmitted through a preamble and so on of a physical layer. The preamble of the physical layer may be a signaling signal included in a broadcast signal and may correspond to signaling in the physical layer. The preamble of the physical layer may mainly include information for acquisition of data, a broadcast frame, a data pipe, and/or a transmission parameter that are included in a broadcast signal.

The receiver checks configuration of an emergency alert channel (EAC) through physical layer signaling of the receiver and decodes the EAC to acquire EAT. Here, the EAC may correspond to the aforementioned dedicated channel.

The receiver checks the received EAT, extracts a CAP message, and transmits the CAP message to a CAP parser.

The receiver decodes a corresponding DP and receives service data when service information associated with the emergency alert is present in the EAT. The EAT may include information for identification of a DP for transmitting a service associated with the emergency alert.

When information associated with NRT service data is present in the EAT or the CAP message, the receiver receives the information through a broadband.

FIG. 79 is a diagram illustrating syntax of a fast information channel (FIC) according to an embodiment of the present invention.

Information included in the FIC may be transmitted in the form of fast information table (FIT).

Information included in the FIT may be transmitted in the form of XML and/or section table.

The FIT may include table_id information, FIT_data_version information, num_broadcast information, broadcast_id information, delivery_system_id information, base_DP_id information, base_DP_version information, num_service information, service_id information, service_category information, service_hidden_flag information, SP_indicator information, num_component information, component_id information, DP_id information, context_id information, RoHC_init_descriptor, context_profile information, max_cid information, and/or large_cid information.

The table_id information indicates that a corresponding table section refers to fast information table.

The FIT_data_version information may indicate version information about syntax and semantics contained in the fast information table. The receiver may determine whether signaling contained in the corresponding fast information table is processed, using the FIT_data_version information. The receiver may determine whether information of pre-stored FIC is updated, using the information.

The num_broadcast information may indicate the number of broadcasters that transmit a broadcast service and/or content through a corresponding frequency or a transmitted transport frame.

The broadcast_id information may indicate a unique identifier of a broadcaster that transmits a broadcast service and/or content through a corresponding frequency or a transmitted transport frame. In the case of a broadcaster that transmits MPEG-2 TS-based data, broadcast_id may have a value such as transport_stream_id of MPEG-2 TS.

The delivery_system_id information may indicate an identifier for a broadcast transmission system that applies and processes the same transmission parameter on a broadcast network that performs transmission.

The base_DP_id information is information for identification of a base DP in a broadcast signal. The base DP may refer to a DP that transmits service signaling including overhead reduction and/or program specific information/system information (PSI/SI) of a broadcaster corresponding to broadcast_id. Alternatively, the base_DP_id information may refer to a representative DP that can decode a component included in a broadcast service in the corresponding broadcaster.

The base_DP_version information may refer to version information about data transmitted through a base DP. For example, when service signaling such as PSI/SI and so on is transmitted through the base DP, if service signaling is changed, a value of the base_DP_version information may be increased one by one.

The num_service information may refer to the number of broadcast services transmitted from a broadcaster corresponding to the broadcast_id in a corresponding frequency or a transport frame.

The service_id information may be used as an identifier for identification of a broadcast service.

The service_category information may refer to a category of a broadcast service. According to a value of a corresponding field, the service_category information may have the following meaning. When a value of the service_category information is 0x01, the service_category information may refer to a basic TV, when the value of the service_category information is 0x02, the service_category information may refer to a basic radio, when the value of the service_category information is 0x03, the service_category information may refer to an RI service, when the value of the service_category information is 0x08, the service_category information may refer to a service guide, and when the value of the service_category information is 0x09, the service_category information may refer to emergency alerting.

The service_hidden_flag information may indicate whether a corresponding broadcast service is hidden. When the service is hidden, the broadcast service may be a test service or a self-used service and may be processed to be disregarded or hidden from a service list by a broadcast receiver.

The SP_indicator information may indicate whether service protection is applied to one or more components in a corresponding broadcast service.

The num_component information may indicate the number of components included in a corresponding broadcast service.

The component_id information may be used as an identifier for identification of a corresponding component in a broadcast service.

The DP_id information may be used as an identifier indicating a DP that transmits a corresponding component.

The RoHC_init_descriptor may include information associated with overhead reduction and/or header recovery. The RoHC_init_descriptor may include information for identification of a header compression method used in a transmission terminal.

The context_id information may represent a context corresponding to a following RoHC related field. The context_id information may correspond to a context identifier (CID).

The context_profile information may represent a range of a protocol for compression of a header in RoHC. When a compressor and a decompressor have the same profile, it is possible to compress and restore a stream in the RoHC.

The max_cid information is used for indicating a maximum value of a CID to a decompressor.

The large_cid information has a boolean value and indicates whether a short CID (0 to 15) or an embedded CID (0 to 16383) is used for CID configuration. Accordingly, the sized of byte for representing the CID is determined together.

FIG. 80 is a diagram illustrating syntax of an emergency alert table (EAT) according to an embodiment of the present invention.

Information associated with emergency alert may be transmitted through the EAC. The EAC may correspond to the aforementioned dedicated channel.

The EAT according to an embodiment of the present invention may include EAT_protocol_version information, automatic_tuning_flag information, num_EAS_messages information, EAS_message_id information, EAS_IP_version_flag information, EAS_message_transfer_type information, EAS_message_encoding_type information, EAS_NRT_flag information, EAS_message_length information, EAS_message_byte information, IP_address information, UDP_port_num information, DP_id information, automatic_tuning_channel_number information, automatic_tuning_DP_id information, automatic_tuning_service_id information, and/or EAS_NRT_service_id information.

The EAT_protocol_version information indicates a protocol version of received EAT.

The automatic_tuning_flag information indicates whether a receiver automatically performs channel conversion.

The num_EAS_messages information indicates the number of messages contained in the EAT.

The EAS_message_id information is information for identification of each EAS message.

The EAS_IP_version_flag information indicates IPv4 when a value of the EAS_IP_version_flag information is 0, and indicates IPv6 when a value of the EAS_IP_version_flag information is 1.

The EAS_message_transfer_type information indicates the form in which an EAS message is transmitted. When a value of the EAS_message_transfer_type information is 000, the EAS_message_transfer_type information indicates a not specified state, when a value of the EAS_message_transfer_type information is 001, the EAS_message_transfer_type information indicates a no alert message (only AV content), and when a value of the EAS_message_transfer_type information is 010, the EAS_message_transfer_type information indicates that an EAS message is contained in corresponding EAT. To this end, a length field and a field about the corresponding EAS message are added. When a value of the EAS_message_transfer_type information is 011, the EAS_message_transfer_type information indicates that the EAS message is transmitted through a data pipe. The EAS may be transmitted in the form of IP datagram in a data pipe. To this end, IP address, UDP port information, and DP information of a transmitted physical layer may be added.

The EAS_message_encoding_type information indicates information about an encoding type of an emergence alert message. For example, when a value of the EAS_message_encoding_type information is 000, the EAS_message_encoding_type information indicates a not specific state, when a value of the EAS_message_encoding_type information is 001, the EAS_message_encoding_type information indicates No Encoding, when a value of the EAS_message_encoding_type information is 010, the EAS_message_encoding_type information indicates DEFLATE algorithm (RFC1951), and 001 to 111 among values of the EAS_message_encoding_type information may be reserved for other encoding types.

The EAS_NRT_flag information indicates whether NRT contents and/or NRT data associated with a received message is present. When a value of the EAS_NRT_flag information is 0, the EAS_NRT_flag information indicates that NRT contents and/or NRT data associated with a received emergency message is not present, and when a value of the EAS_NRT_flag information is 1, the EAS_NRT_flag information indicates that NRT contents and/or NRT data associated with a received emergency message is present.

The EAS_message_length information indicates a length of an EAS message.

The EAS_message_byte information includes content of an EAS message.

The IP_address information indicates an IP address of an IP address for transmission of an EAS message.

The UDP_port_num information indicates a UDP port number for transmission of an EAS message.

The DP_id information identifies a data pipe that transmits an EAS message.

The automatic_tuning_channel_number information includes information about a number of a channel to be converted.

The automatic_tuning_DP_id information is information for identification of a data pipe that transmits corresponding content.

The automatic_tuning_service_id information is information for identification of a service to which corresponding content belongs.

The EAS_NRT_service_id information is information for identification of an NRT service corresponding to the case in which NRT contents and data associated with a received emergency alert message and transmitted, that is, the case in which an EAS_NRT_flag is enabled.

FIG. 81 is a diagram illustrating a packet transmitted to a data pipe according to an embodiment of the present invention.

According to an embodiment of the present invention, configuration of a packet in a link layer is newly defined so as to generate a compatible link layer packet irrespective of change in protocol of a upper layer or the link layer or a lower layer of the link layer.

The link layer packet according to an embodiment of the present invention may be transmitted to a normal DP and/or a base DP.

The link layer packet may include a fixed header, an expansion header, and/or a payload.

The fixed header is a header with a fixed size and the expansion header is a header, the size of which can be changed according to configuration of the packet of the upper layer. The payload is a region in which data of the upper layer is transmitted.

A header (the fixed header or the expansion header) of a packet may include a field indicating a type of the payload of the packet. In the case of the fixed header, first 3 bits (packet type) of 1 byte may include data for identification of a packet type of the upper layer, and the remaining 5 bits may be used as an indicator part. The indicator part may include data for identification of a configuring method of a payload and/or configuration information of the expansion header and may be changed according to a packet type.

A table shown in the diagram represents a type of a upper layer included in a payload according to a value of a packet type.

According to system configuration, an IP packet and/or an RoHC packet of the payload may be transmitted through a DP, and a signaling packet may be transmitted through a base DP. Accordingly, when a plurality of packets are mixed and transmitted, packet type values may also be applied so as to differentiate a data packet and a signaling packet.

When a packet type value is 000, an IP packet of IPv4 is included in a payload.

When a packet type value is 001, an IP packet of IPv6 is included in a payload.

When a packet type value is 010, a compressed IP packet is included in a payload. The compressed IP packet may include an IP packet to which header compression is applied.

When a packet type value is 110, a packet including signaling data is included in a payload.

When a packet type value is 111, a framed packet type is included in a payload.

FIG. 82 is a diagram illustrating a detailed processing operation of a signal and/or data in each protocol stack of a transmitter when a logical data path of a physical layer includes a dedicated channel, a base DP, and a normal data DP, according to another embodiment of the present invention.

In one frequency band, one or more broadcasters may provide broadcast services. A broadcaster transmits multiple broadcast services and one broadcast service may include one or more components. A user may receive content in units of broadcast services.

In a broadcast system, a session-based transmission protocol may be used to support IP hybrid broadcast and the contents of signaling delivered to each signaling path may be determined according to the structure of the corresponding transmission protocol.

As described above, data related to the FIC and/or the EAC may be transmitted/received over the dedicated channel. In the broadcast system, a base DP and a normal DP may be used to distinguish therebetween.

Configuration information of the FIC and/or EAC may be included in physical layer signaling (or a transmission parameter). A link layer may format signaling according to characteristics of a corresponding channel. Transmission of data to a specific channel of a physical layer may be performed from a logical point of view and actual operation may be performed according to characteristics of a physical layer.

The FIC may include information about services of each broadcaster, transmitted in a corresponding frequency and information about paths for receiving the services. The FIC may include information for service acquisition and may be referred to as service acquisition information.

The FIC and/or the EAC may be included in link layer signaling.

Link layer signaling may include the following information.

System Parameter—A parameter related to a transmitter or a parameter related to a broadcaster that provides a service in a corresponding channel.

Link layer: Context information associated with IP header compression and an ID of a DP to which a corresponding context is applied.

Upper layer: IP address and UDP port number, service and component information, emergency alert information, and a mapping relationship between an ID address, a UDP port number, a session ID, and a DP of a packet stream and signaling transmitted in an IP layer.

As described above, one or more broadcast services are transmitted in one frequency band, the receiver does not need to decode all DPs and it is efficient to pre-check signaling information and to decode only a DP related to a necessary service.

In this case, referring to the drawing, the broadcast system may provide and acquire information for mapping a DP and a service, using the FIC and/or the base DP.

A process of processing a broadcast signal or broadcast data in a transmitter of the drawing will now be described. One or more broadcasters (broadcasters #1 to #N) may process component signaling and/or data for one or more broadcast services so as to be transmitted through one or more sessions. One broadcast service may be transmitted through one or more sessions. The broadcast service may include one or more components included in the broadcast service and/or signaling information for the broadcast service. Component signaling may include information used to acquire components included in the broadcast service in a receiver. Service signaling, component signaling, and/or data for one or more broadcast services may be transmitted to a link layer through processing in an IP layer.

In the link layer, the transmitter performs overhead reduction when overhead reduction for an IP packet is needed and generates related information as link layer signaling. Link layer signaling may include a system parameter specifying the broadcast system, in addition to the above-described information. The transmitter may process an IP packet in a link layer processing procedure and transmit the processed IP packet to a physical layer in the form of one or more DPs.

The transmitter may transmit link layer signaling to the receiver in the form or configuration of an FIC and/or an EAC. Meanwhile, the transmitter may also transmit link layer signaling to the base DP through an encapsulation procedure of the link layer.

FIG. 83 is a diagram illustrating a detailed processing operation of a signal and/or data in each protocol stack of a receiver when a logical data path of a physical layer includes a dedicated channel, a base DP, and a normal data DP, according to another embodiment of the present invention.

If a user selects or changes a service desired to be received, a receiver tunes to a corresponding frequency. The receiver reads information stored in a DB etc. in association with a corresponding channel. The information stored in the DB etc. of the receiver may be information included upon acquiring an FIC and/or an EAC during initial channel scan. Alternatively, the receiver may extract transmitted information as described above in this specification.

The receiver may receive the FIC and/or the EAC, receive information about a channel that the receiver desires to access, and then update information pre-stored in the DB. The receiver may acquire components for a service selected by a user and information about a mapping relationship of a DP transmitted by each component or acquire a base DP and/or a normal DP through which signaling necessary to obtain such information is transmitted. Meanwhile, when it is judged that there is no change in corresponding information using version information of the FIC or information identifying whether to require additional update of a dedicated channel, the receiver may omit a procedure of decoding or parsing the received FIC and/or EAC.

The receiver may acquire a link layer signaling packet including link layer signaling information by decoding a base DP and/or a DP through which signaling information is transmitted, based on information transmitted through the FIC. The receiver may use, when necessary, the received link layer signaling information by a combination with signaling information (e.g., receiver information in the drawing) received through the dedicated channel.

The receiver may acquire information about a DP for receiving a service selected by the user among multiple DPs that are being transmitted over a current channel and overhead reduction information about a packet stream of the corresponding DP, using the FIC and/or the link layer signaling information.

When the information about the DP for receiving the selected service is transmitted through upper layer signaling, the receiver may acquire signaling information stored in the DB and/or the shared memory as described above and then acquire information about a DP to be decoded, indicated by the corresponding signaling information.

When the link layer signaling information and normal data (e.g., data included in broadcast content) are transmitted through the same DP or only one DP is used for transmission of the link layer signaling information and normal data, the receiver may temporarily store the normal data transmitted through the DP in a device such as a buffer while the signaling information is decoded and/or parsed.

The receiver may acquire the base DP and/or the DP through which the signaling information is transmitted, acquire overhead reduction information about a DP to be received, perform decapsulation and/or header recovery for a packet stream received in a normal DP, using the acquired overhead information, process the packet stream in the form of an IP packet stream, and transmit the IP packet stream to a upper layer of the receiver.

FIG. 84 is a diagram illustrating a syntax of an FIC according to another embodiment of the present invention.

Information included in the FIC described in this drawing may be selectively combined with other information included in the FIC and may configure the FIC.

The receiver may rapidly acquire information about a channel, using the information included in the FIC. The receiver may acquire bootstrap related information using the information included in the FIC. The FIC may include information for fast channel scan and/or fast service acquisition. The FIC may be referred to by other names, for example, a service list table or service acquisition information. The FIC may be transmitted by being included in an IP packet in an IP layer according to a broadcast system. In this case, an IP address and/or a UDP port number, transmitting the FIC, may be fixed to specific values and the receiver may recognize that the IP packet transmitted with the corresponding IP address and/or UDP port number includes the FIC, without an additional processing procedure.

The FIC may include FIC_protocol_version information, transport_stream_id information, num_partitions information, partition_id information, partition_protocol_version information, num_services information, service_id information, service_data_version information, service_channel_number information, service_category information, service_status information, service_distribution information, sp_indicator information, IP_version_flag information, SSC_source_IP_address_flag information, SSC_source_IP_address information, SSC_destination_IP_address information, SSC_destination_UDP_port information, SSC_TSI information, SSC DP_ID information, num_partition_level_descriptors information, partition_level_descriptor( ) information, num_FIC_level_descriptors information, and/or FIC_level_descriptor( ) information.

FIC_protocol_version information represents a version of a protocol of an FIC.

transport_stream_id information identifies a broadcast stream. transport_stream_id information may be used as information for identifying a broadcaster.

num_partitions information represents the number of partitions in a broadcast stream. The broadcast stream may be transmitted after being divided into one or more partitions. Each partition may include one or more DPs. The DPs included in each partition may be used by one broadcaster. In this case, the partition may be defined as a data transmission unit allocated to each broadcaster.

partition_id information identifies a partition. partition_id information may identify a broadcaster.

partition_protocol_version information represents a version of a protocol of a partition.

num_services information represents the number of services included in a partition. A service may include one or more components.

service_id information identifies a service.

service_data_version information represents change when a signaling table (signaling information) for a service is changed or a service entry for a service signaled by an FIC is changed. service_data_version information may increment a value thereof whenever such change is present.

service_channel_number information represents a channel number of a service.

service_category information represents a category of a service. The category of a service includes A/V content, audio content, an electronic service guide (ESG), and/or content on demand (CoD).

service_status information represents a state of a service. A state of a service may include an active or suspended state and a hidden or shown state. The state of a service may include an inactive state. In the inactive state, broadcast content is not currently provided but may be provided later. Accordingly, when a viewer scans a channel in a receiver, the receiver may not show a scan result for a corresponding service to the viewer.

service_distribution information represents a distribution state of data for a service. For example, service_distribution information may represent that entire data of a service is included in one partition, partial data of a service is not included in a current partition but content is presentable only by data in this partition, another partition is needed to present content, or another broadcast stream is needed to present content.

sp_indicator information identifies whether service protection has been applied. sp_indicator information may identify, for example, for meaningful presentation, whether one or more necessary components are protected (e.g., a state in which a component is encrypted).

IP_version_flag information identifies whether an IP address indicated by SSC_source_IP_address information and/or SSC_destination_IP_address information is an IPv4 address or an IPv6 address.

SSC_source_IP_address_flag information identifies whether SSC_source_IP_address information is present.

SSC_source_IP_address information represents a source IP address of an IP datagram that transmits signaling information for a service. The signaling information for a service may be referred to as service layer signaling. Service layer signaling includes information specifying a broadcast service. For example, service layer signaling may include information identifying a data unit (a session, a DP, or a packet) that transmits components constituting a broadcast service.

SSC_destination_IP_address information represents a destination IP address of an IP datagram (or channel) that transmits signaling information for a service.

SSC_destination_UDP_port information represents a destination UDP port number for a UDP/IP stream that transmits signaling information for a service.

SSC_TSI information represents a transport session identifier (TSI) of an LCT channel (or session) that transmits signaling information (or a signaling table) for a service.

SSC_DP_ID information represents an ID for identifying a DP including signaling information (or a signaling table) for a service. As a DP including the signaling information, the most robust DP in a broadcast transmission process may be allocated.

num_partition_level_descriptors information identifies the number of descriptors of a partition level for a partition.

partition_level_descriptor( ) information includes zero or more descriptors that provide additional information for a partition.

num_FIC_level_descriptors information represents the number of descriptors of an FIC level for an FIC.

FIC_level_descriptor( ) information includes zero or more descriptors that provide additional information for an FIC.

FIG. 85 is a diagram illustrating signaling_Information_Part( ) according to an embodiment of the present invention.

A broadcast system may add additional information to an extended header part in the case of a packet for transmitting signaling information in a structure of a packet transmitted through the above-described DP. Such additional information will be referred to as Signaling_Information_Part( ).

Signaling_Information_Part( ) may include information used to determine a processing module (or processor) for received signaling information. In a system configuration procedure, the broadcast system may adjust the number of fields indicating information and the number of bits allocated to each field, in a byte allocated to Signaling_Information_Part( ). When signaling information is transmitted through multiplexing, a receiver may use information included in Signaling_Information_Part( ) to determine whether corresponding signaling information is processed and determine to which signaling processing module signaling information should be transmitted.

Signaling_Information_Part( ) may include Signaling_Class information, Information_Type information, and/or signaling format information.

Signaling_Class information may represent a class of transmitted signaling information. Signaling information may correspond to an FIC, an EAC, link layer signaling information, service signaling information, and/or upper layer signaling information. Mapping for a class of signaling information indicated by each value of configuration of the number of bits of a field of Signaling_Class information may be determined according to system design.

Information_Type information may be used to indicate details of signaling information identified by signaling class information. Meaning of a value indicated by Information_Type information may be additionally defined according to class of signaling information indicated by Signaling_Class information.

Signaling format information represents a form (or format) of signaling information configured in a payload. The signaling format information may identify formats of different types of signaling information illustrated in the drawing and identify a format of additionally designated signaling information.

Signaling_Information_Part( ) of (a) and (b) illustrated in the drawing is one embodiment and the number of bits allocated to each field thereof may be adjusted according to characteristics of the broadcast system.

Signaling_Information_Part( ) as in (a) of the drawing may include signaling class information and/or signaling format information. Signaling_Information_Part( ) may be used when a type of signaling information need not be designated or an information type can be judged in signaling information. Alternatively, when only one signaling format is used or when an additional protocol for signaling is present so that signaling formats are always equal, only a 4-bit signaling class field may be used without configuring a signaling field and the other fields may be reserved for later use or an 8-bit signaling class maybe configured to support various types of signaling.

Signaling_Information_Part( ) as in (b) of the drawing may further include information type information for indicating a type or characteristic of more detailed information in a signaling class when the signaling class is designated and may also include signaling format information. Signaling class information and information type information may be used to determine decapsulation of signaling information or a processing procedure of corresponding signaling. A detailed structure or processing of link layer signaling may refer to the above description and a description which will be given below.

FIG. 86 is a diagram illustrating a procedure for controlling an operation mode of a transmitter and/or a receiver in a link layer according to an embodiment of the present invention.

When the operation mode of the transmitter or the receiver of the link layer is determined, a broadcast system can be more efficiently used and can be flexibly designed. The method of controlling the link layer mode proposed according to the present invention can dynamically convert a mode of a link layer in order to efficiently manage a system bandwidth and processing time. In addition, the method of controlling the link layer mode according to the present invention may easily cope with the case in which a specific mode needs to be supported due to change in a physical layer or on the other hand, the specific mode does not have to be changed any more. In addition, the method of controlling the link layer mode according to the present invention may also allow a broadcast system to easily satisfy requirements of a corresponding broadcaster when a broadcaster providing a broadcast service intends to designate a method of transmitting a corresponding service.

The method of controlling the mode of the link layer may be configured to be performed only in a link layer or to be performed via change in data configuration in the link layer. In this case, it is possible to perform an independent operation of each layer in a network layer and/or a physical layer without embodiment of a separate function. In the mode of the link layer proposed according to the present invention, it is possible to control the mode with signaling or parameters in a system without changing a system in order to satisfy configuration of a physical layer. A specific mode may be performed only when processing of corresponding input is supported in a physical layer.

The diagram is a flowchart illustrating processing of signal and/or data in an IP layer, a link layer, and a physical layer by a transmitter and/or a receiver.

A function block (which may be embodied as hardware and/or software) for mode control may be added to the link layer and may manage parameter and/or signaling information for determination of whether a packet is processed. The link layer may determine whether a corresponding function is performed during processing of a packet stream using information of a mode control functional block.

First, an operation of the transmitter will be described.

When an IP is input to a link layer, the transmitter determines whether overhead reduction (j16020) is performed using a mode control parameter (j16005). The mode control parameter may be generated by a service provider in the transmitter. The mode control parameter will be described below in detail.

When the overhead reduction (j16020) is performed, information about overhead reduction is generated and is added to link layer signaling (j16060) information. The link layer signaling (j16060) information may include all or some of mode control parameters. The link layer signaling (j16060) information may be transmitted in the form of link layer signaling packet. The link layer signaling packet may be mapped to a DP and transmitted to the receiver, but may not be mapped to the DP and may be transmitted to the receiver in the form of link layer signaling packet through a predetermined region of a broadcast signal.

A packet stream on which the overhead reduction (j16020) is performed is encapsulated (j16030) and input to a DP of a physical layer (j16040). When overhead reduction is not performed, whether encapsulation is performed is re-determined (j16050).

A packet stream on which the encapsulation (j16030) is performed is input to a DP (j16040) of a physical layer. In this case, the physical layer performs an operation for processing a general packet (a link layer packet). When overhead reduction and encapsulation are not performed, an IP packet is transmitted directly to a physical layer. In this case, the physical layer performs an operation for processing the IP packet. When the IP packet is directly transmitted, a parameter may be applied to perform the operation only when the physical layer support IP packet input. That is, a value of a mode control parameter may be configured to be adjusted such that a process of transmitting an IP packet directly to a physical layer is not performed when the physical layer does not support processing of an IP packet.

The transmitter transmits a broadcast signal on which this process is performed, to the receiver.

An operation of the receiver will be described below.

When a specific DP is selected for the reason such channel change and so on according to user manipulation and a corresponding DP receives a packet stream (j16110), the receiver may check a mode in which a packet is generated, using a header and/or signaling information of the packet stream (j16120). When the operation mode during transmission of the corresponding DP is checked, decapsulation (j16130) and overhead reduction (j16140) processes are performed through a receiving operating process of a link layer and then an IP packet is transmitted to a upper layer. The overhead reduction (j16140) process may include an overhead recovery process.

FIG. 87 is a diagram illustrating an operation in a link layer according to a value of a flag and a type of a packet transmitted to a physical layer according to an embodiment of the present invention.

In order to determine an operation mode of the link layer, the aforementioned signaling method may be used. Signaling information associated with the method may be transmitted directly to a receiver. In this case, the aforementioned signaling data or link layer signaling packet may include mode control that will be described below and related information.

In consideration of the complexity of the receiver, an operation mode of the link layer may be indirectly indicated to the receiver.

The following two flags may be configured with regard to control of an operation mode.

-   -   Header compression flag (HCF): This may be a flag for         determination of whether header compression is applied to a         corresponding link layer and may have a value indicating enable         or disable.     -   Encapsulation flag (EF): This may be a flag for determination of         whether encapsulation is applied in a corresponding link layer         and may have a value indicating enable or disable. However, when         encapsulation needs to be performed according to a header         compression scheme, the EF may be defined to be dependent upon a         HCF.

A value mapped to each flag may be applied according to system configuration as long as the value represents Enable and Disable, and a bit number allocated to each flag can be changed. According to an embodiment of the present invention, an enable value may be mapped to 1 and a disable value may be mapped to 0.

The diagram shows whether header compression and encapsulation included in a link layer are performed according to values of HCF and EF and in this case, a packet format transmitted to a physical layer. That is, according to an embodiment of the present invention, the receiver can know a type of a packet input to the physical layer as information about the HCF and the EF.

FIG. 88 is a diagram a descriptor for signaling a mode control parameter according to an embodiment of the present invention.

Flags as information about mode control in a link layer may be signaling information, generated by the transmitter in the form of descriptor, and transmitted to the receiver. Signaling including a flag as information about mode control may be used to control an operation mode in a transmitter of a headend terminal, and whether a flag as information about mode control is included in signaling transmitted to the receiver may be optionally selected.

When signaling including a flag as information about mode control is transmitted to the receiver, the receiver may directly select an operation mode about a corresponding DP and perform a packet decapsulation operation. When signaling including a flag as information about mode control is not transmitted to the receiver, the receiver can determine a mode in which the signaling is transmitted, using physical layer signaling or field information of a packet header, which is transmitted to the receiver.

The link layer mode control description according to an embodiment of the present invention may include DP_id information, HCF information, and/or EF information. The link layer mode control description may be included in a transmission parameter in the aforementioned FIC, link layer signaling packet, signaling via a dedicated channel, PSI/SI, and/or physical layer.

The DP_id information identifies a DP to which a mode in a link layer is applied.

The HCF information identifies whether header compression is applied in the DP identified by the DP_id information.

The EF information identifies whether encapsulation is performed on the DP identified by the DP_id information.

FIG. 89 is a diagram illustrating an operation of a transmitter for controlling a operation mode according to an embodiment of the present invention.

Although not illustrated in the diagram, prior to a processing process of al ink layer, a transmitter may perform processing in a upper layer (e.g., an IP layer). The transmitter may generate an IP packet including broadcast data for a broadcast service.

The transmitter parses or generates a system parameter (JS19010). Here, the system parameter may correspond to the aforementioned signaling data and signaling information.

The transmitter may receive or set mode control related parameter or signaling information during a broadcast data processing process in a link layer and sets a flag value associated with operation mode control (JS19020). The transmitter may perform this operation after the header compression operation or the encapsulation operation. That is, the transmitter may perform the header compression or encapsulation operation and generate information associated with this operation.

The transmitter acquires a packet of a upper layer that needs to be transmitted through a broadcast signal (JS19030). Here, the packet of the upper layer may correspond to an IP packet.

The transmitter checks HCF in order to determine whether header compression is applied to the packet of the upper layer (JS19040).

When the HCF is enabled, the transmitter applies the header compression to the packet of the upper layer (JS19050). After header compression is performed, the transmitter may generate the HCF. The HCF may be used to signal whether header compression is applied, to the receiver.

The transmitter performs encapsulation on the packet of the upper layer to which header compression is applied to generate a link layer packet (JS19060). After the encapsulation process is performed, the transmitter may generate an EF. The EF may be used to signal whether encapsulation is applied to the upper layer packet, to the receiver.

The transmitter transmits the link layer packet to a physical layer processor (JS19070). Then the physical layer processor generates a broadcast signal including the link layer packet and transmits the broadcast signal to the receiver.

When the HCF is disabled, the transmitter checks the EF in order to determine whether encapsulation is applied (JS19080).

When the EF is enabled, the transmitter performs encapsulation on the upper layer packet (JS19090). When the EF is disabled, the transmitter does not perform separate processing on the corresponding packet stream. The transmitter transmits the packet stream (link layer packet) on which processing is completed in the link layer, to a physical layer (JS19070). Header compression, encapsulation, and/or generation of link layer may be performed by a link layer packet generator (i.e. link layer processor) in the transmitter.

The transmitter may generate service signaling channel (SCC) data. The service signaling channel data may be generated by a service signaling data encoder. The service signaling data encoder may be included in a link layer processor and may present separately from the link layer processor. The service signaling channel data may include the aforementioned FIC and/or EAT. The service signaling channel data may be transmitted to the aforementioned dedicated channel.

FIG. 90 is a diagram illustrating an operation of a receiver for processing a broadcast signal according to an operation mode according to an embodiment of the present invention.

A receiver may receive information associated with an operation mode in a link layer together with a packet stream.

The receiver receives signaling information and/or channel information (JS20010). Here, a description of the signaling information and/or the channel information is replaced with the above description.

The receiver selects a DP for receiving and processing according to the signaling information and/or the channel information (JS20020).

The receiver performs decoding of a physical layer on the selected DP and receives a packet stream of a link layer (JS20030).

The receiver checks whether link layer mode control related signaling is included in the received signaling (JS20040).

When the receiver receives the link layer mode related information, the receiver checks an EF (JS20050).

When the EF is enabled, the receiver performs a decapsulation process on a link layer packet (JS20060).

The receiver checks an HCF after decapsulation of the packet, and performs a header decompression process when the HCF is enabled (JS20080).

The receiver transmits the packet on which header decompression is performed, to a upper layer (e.g., an IP layer) (JS20090). During the aforementioned process, when the HCF and the EF are disabled, the receiver recognizes the processed packet stream as an IP packet and transmits the corresponding packet to the IP layer.

When the receiver does not receive link layer mode related information or a corresponding system does not transmit the link layer mode related information to the receiver, the following operation is performed.

The receiver receives signaling information and/or channel information (JS20010) and selects a DP for reception and processing according to corresponding information (JS20020). The receiver performs decoding of the physical layer on the selected DP to acquire a packet stream (JS20030).

The receiver checks whether the received signaling includes link layer mode control related signaling (JS20040).

Since the receiver does not receive link layer mode related signaling, the receiver checks a format of the packet transmitted using physical layer signaling, etc. (JS20100). Here, the physical layer signaling information may include information for identification of a type of the packet included in a payload of the DP. When the packet transmitted from the physical layer is an IP packet, the receiver transmits the packet to the IP layer without a separate process in a link layer.

When a packet transmitted from a physical layer is a packet on which encapsulation is performed, the receiver performs a decapsulation process on the corresponding packet (JS20110).

The receiver checks the form of a packet included in a payload using information such as a header, etc. of the link layer packet during the decapsulation process (JS20120), and the receiver transmits the corresponding packet to the IP layer processor when the payload is an IP packet.

When the payload of the link layer packet is a compressed IP, the receiver performs a decompression process on the corresponding packet (JS20130).

The receiver transmits the IP packet to an IP layer processor (JS20140).

FIG. 91 is a diagram illustrating information for identifying an encapsulation mode according to an embodiment of the present invention.

In a broadcast system, when processing in a link layer operates in one or more modes, a procedure for determining as which mode processing in the link layer operates (in a transmitter and/or a receiver) may be needed. In a procedure of establishing a transmission link between the transmitter and the receiver, the transmitter and/or the receiver may confirm configuration information of the link layer. This case may correspond to the case in which the receiver is initially set up or performs a scan procedure for a service or a mobile receiver newly enters an area within a transmission radius of the transmitter. This procedure may be referred to as an initialization procedure or a bootstrapping procedure. This procedure may be configured as a partial process of a procedure supported by the system without being configured by an additional procedure. In this specification, this procedure will be referred to as an initialization procedure.

Parameters needed in the initialization procedure may be determined according to functions supported by a corresponding link layer and types of operating modes possessed by each function. A description will be given hereinafter of the parameters capable of determining functions constituting the link layer and operation modes according to the functions.

The above-described drawing illustrates parameters for identifying an encapsulation mode.

When a procedure for encapsulating a packet in a link layer or a upper layer (e.g., an IP layer) can be configured, indexes are assigned to respective encapsulation modes and a proper field value may be allocated to each index. The drawing illustrates an embodiment of a field value mapped to each encapsulation mode. While it is assumed that a 2-bit field value is assigned in this embodiment, the field value may be expanded within a range permitted by the system in actual implementation, when more supportable encapsulation modes are present.

In this embodiment, if a field of information indicating an encapsulation mode is set to ‘00’, the corresponding information may represent that encapsulation in a link layer is bypasses and not performed. If a field of information indicating an encapsulation mode is set to ‘01’, the corresponding information may represent that data is processed by a first encapsulation scheme in the link layer. If a field of information indicating an encapsulation mode is set to ‘10’, the corresponding information may represent that data is processed by a second encapsulation scheme in the link layer. If a field of information indicating an encapsulation mode is set to ‘11’, the corresponding information may represent that data is processed by a third encapsulation scheme in the link layer.

FIG. 92 is a diagram illustrating information for identifying a header compression mode according to an embodiment of the present invention.

Processing in a link layer may include a function of header compression of an IP packet. If a few IP header compression schemes are capable of being supported in the link layer, a transmitter may determine which scheme the transmitter is to use.

Determination of a header compression mode generally accompanies an encapsulation function. Therefore, when the encapsulation mode is disabled, the header compression mode may also be disabled. The above-described drawing illustrates an embodiment of a field value mapped to each header compression mode. While it is assumed that a 3-bit field value is assigned in this embodiment, the field value may be expanded or shortened within a range permitted by the system in actual implementation according to a supportable header compression mode.

In this embodiment, if a field of information indicating the header compression mode is set to ‘000’, the corresponding information may indicate that header compression processing for data is not performed in a link layer. If a field of information indicating the header compression mode is set to ‘001’, the corresponding information may indicate that header compression processing for data in the link layer uses an RoHC scheme. If a field of information indicating the header compression mode is set to ‘010’, the corresponding information may indicate that header compression processing for data in the link layer uses a second RoHC scheme. If a field of information indicating the header compression mode is set to ‘011’, the corresponding information may indicate that header compression processing for data in the link layer uses a third RoHC scheme. If a field of information indicating the header compression mode is set to ‘100’ to ‘111’, the corresponding information may indicate that header compressing for data is reserved as a region for identifying a new header compression processing scheme for data in the link layer.

FIG. 93 is a diagram illustrating information for identifying a packet reconfiguration mode according to an embodiment of the present invention.

To apply a header compression scheme to a unidirectional link such as a broadcast system, the broadcast system (transmitter and/or receiver) needs to rapidly acquire context information. The broadcast system may transmit/receive a packet stream after a header compression procedure in an out-of-band form through reconfiguration of partial compressed packets and/or extraction of context information. In the present invention, a mode for reconfiguring a packet or performing processing such as addition of information capable of identifying the structure of the packet may be referred to as a packet reconfiguration mode.

The packet reconfiguration mode may use a few schemes and the broadcast system may designate a corresponding scheme in an initialization procedure of a link layer. The above-described drawing illustrates an embodiment of an index and a field value mapped to the packet reconfiguration mode. While it is assumed that a 2-bit field value is assigned in this embodiment, the field value may be expanded or shortened within a range permitted by the system in actual implementation according to a supportable packet reconfiguration mode.

In this embodiment, if a field of information indicating the packet reconfiguration mode is set to ‘00’, corresponding information may represent that reconfiguration for a packet transmitting data is not performed in a link layer. If a field of information indicating the packet reconfiguration mode is set to ‘01’, corresponding information may represent that a first reconfiguration scheme is performed for a packet transmitting data in the link layer. If a field of information indicating the packet reconfiguration mode is set to ‘10’, corresponding information may represent that a second reconfiguration scheme is performed for a packet transmitting data in the link layer. If a field of information indicating the packet reconfiguration mode is set to ‘11’, corresponding information may represent that a third reconfiguration scheme is performed for a packet transmitting data in the link layer.

FIG. 94 is a diagram illustrating a context transmission mode according to an embodiment of the present invention.

A transmission scheme of the above-described context information may include one or more transmission modes. That is, the broadcast system may transmit the context information in many ways. In the broadcast system, a context transmission mode may be determined according to the system and/or a transmission path of a logical physical layer and information for identifying the context transmission scheme may be signaled. The above-described drawing illustrates an embodiment of an index and a field value mapped to the context transmission mode. While it is assumed that a 3-bit field value is assigned in this embodiment, the field value may be expanded or shortened within a range permitted by the system in actual implementation according to a supportable context transmission mode.

In this embodiment, if a field of information indicating the context transmission mode is set to ‘000’, corresponding field information may represent that context information is transmitted as a first transmission mode. If a field of information indicating the context transmission mode is set to ‘001’, corresponding information may represent that context information is transmitted as a second transmission mode. If a field of information indicating the context transmission mode is set to ‘010’, corresponding information may represent that context information is transmitted as a third transmission mode. If a field of information indicating the context transmission mode is set to ‘011’, corresponding information may represent that context information is transmitted as a fourth transmission mode. If a field of information indicating the context transmission mode is set to ‘100’, corresponding information may represent that context information is transmitted as a fifth transmission mode. If a field of information indicating a context transmission mode is set to ‘101’ to ‘111’, corresponding information may represent that context information is reserved to identify a new transmission mode.

FIG. 95 is a diagram illustrating initialization information when RoHC is applied by a header compression scheme according to an embodiment of the present invention.

While the case in which RoHC is used for header compression has been described by way of example in the present invention, similar initialization information may be used in the broadcast system even when a header compression scheme of other types is used.

In the broadcast system, transmission of initialization information suitable for a corresponding compression scheme according to a header compression mode may be needed. In this embodiment, an initialization parameter for the case in which a header compression mode is set to RoHC is described. Initialization information for RoHC may be used to transmit information about configuration of an RoHC channel which is a link between a compressor and a decompressor.

One RoHC channel may include one or more context information and information commonly applied to all contexts in the RoHC channel may be transmitted/received by being included in the initialization information. A path through which related information is transmitted by applying RoHC may be referred to as an RoHC channel and, generally, the RoHC channel may be mapped to a link. In addition, the RoHC channel may be generally transmitted through one DP and, in this case, the RoHC channel may be expressed using information related to the DP.

The initialization information may include link_id information, max_cid information, large_cids information, num_profiles information, profiles( ) information, num_IP stream information, and/or IP_address( ) information.

link_id information represents an ID of a link (RoHC channel) to which corresponding information is applied. When the link or the RoHC channel is transmitted through one DP, link_id information may be replaced with DP_id.

max_cid information represents a maximum value of a CID. max_cid information may be used to inform a decompressor of the maximum value of the CID.

large_cids information has a Boolean value and identifies whether a short CID (0 to 15) is used or an embedded CID (0 to 16383) is used in configuring a CID. Therefore, a byte size expressing the CID may also be determined.

num_profiles information represents the number of profiles supported in an identified RoHC channel.

profiles( ) information represents a range of a protocol header-compressed in RoHC. Since a compressor and a decompressor should have the same profile in RoHC to compress and recover a stream, a receiver may acquire a parameter of RoHC used in a transmitter from profiles( ) information.

num_IP_stream information represents the number of IP streams transmitted through a channel (e.g., an RoHC channel).

IP_address information represents an address of an IP stream. IP_address information may represent a destination address of a filtered IP stream which is input to an RoHC compressor (transmitter).

FIG. 96 is a diagram illustrating information for identifying link layer signaling path configuration according to an embodiment of the present invention.

In the broadcast system, generally, a path through which signaling information is delivered is designed not to be changed. However, when the system is changed or while replacement between different standards occurs, information about configuration of a physical layer in which link layer signaling information rather than an IP packet is transmitted needs to be signaled. In addition, when a mobile receiver moves between regions covered by transmitters having different configurations, since paths through which link layer signaling information is transmitted may differ, the case in which link layer signaling path information should be transmitted may occur. The above-described drawing illustrates information for identifying a signaling path which is a path through which the link layer signaling information is transmitted/received. Indexes may be expanded or shortened with respect to the link layer signaling information according to a signaling transmission path configured in a physical layer. Separately from configuration in a link layer, operation of a corresponding channel may conform to a procedure of the physical layer.

The above-described drawing illustrates an embodiment in which information about signaling path configuration is allocated to a field value. In this specification, when multiple signaling paths are supported, indexes may be mapped to signaling paths having great importance in order of small values. Signaling paths having priority prioritized according to an index value may also be identified.

Alternatively, the broadcast system may use all signaling paths having higher priority than signaling paths indicated by the information about signaling path configuration. For example, when a signaling path configuration index value is 3, a corresponding field value may be ‘011’ indicating that all of a dedicated data path, a specific signaling channel (FIC), and a specific signaling channel (EAC), priorities of which are 1, 2, and 3, are being used.

Signaling of the above scheme can reduce the amount of data that transmits signaling information.

FIG. 97 is a diagram illustrating information about signaling path configuration by a bit mapping scheme according to an embodiment of the present invention.

The above-described information about signaling path configuration may be transmitted/received through definition of a bit mapping scheme. In this embodiment, allocation of 4 bits to the information about signaling path configuration is considered and signaling paths corresponding to respective bits b1, b2, b3, and b4 may be mapped. If a bit value of each position is 0, this may indicate that a corresponding path is disabled and, if a bit value of each position is 1, this may indicate that a corresponding path is enabled. For example, if a 4-bit signaling path configuration field value is ‘1100’, this may indicate that the broadcast system is using a dedicated DP and a specific signaling channel (FIC) in a link layer.

FIG. 98 is a flowchart illustrating a link layer initialization procedure according to an embodiment of the present invention.

If a receiver is powered on or a mobile receiver enters a transmission region of a new transmitter, the receiver may perform an initialization procedure for all or some system configurations. In this case, an initialization procedure for a link layer may also be performed. Initial setup of the link layer in the receiver, using the above-described initialization parameters may be performed as illustrated in the drawing.

The receiver enters an initialization procedure of a link layer (JS32010).

Upon entering the initialization procedure of the link layer, the receiver selects an encapsulation mode (JS32020). The receiver may select the encapsulation mode using the above-described initialization parameters in this procedure.

The receiver determines whether encapsulation is enabled (JS32030). The receiver may determine whether encapsulation is enabled using the above-described initialization parameters in this procedure.

Generally, since a header compression scheme is applied after the encapsulation procedure, if an encapsulation mode is disabled, the receiver may determine that a header compression mode is disabled (JS32080). In this case, since it is not necessary for the receiver to proceed to the initialization procedure any more, the receiver may immediately transmit data to another layer or transition to a data processing procedure.

The receiver selects a header compression mode (JS32040) when the encapsulation mode is enabled. Upon selecting the header compression mode, the receiver may determine a header compression scheme applied to a packet, using the above-described initialization parameter.

The receiver determines whether header compression is enabled (JS32050). If header compression is disabled, the receiver may immediately transmit data or transition to a data processing procedure.

If header compression is enabled, the receiver selects a packet stream reconfiguration mode and/or a context transmission mode (JS32060 and JS32070) with respect to a corresponding header compression scheme. The receiver may select respective modes using the above-described information in this procedure.

Then, the receiver may transmit data for another processing procedure or perform the data processing procedure.

FIG. 99 is a flowchart illustrating a link layer initialization procedure according to another embodiment of the present invention.

The receiver enters an initialization procedure of a link layer (JS33010).

The receiver identifies link layer signaling path configuration (JS33020). The receiver may identify a path through which link layer signaling information is transmitted, using the above-described information.

The receiver selects an encapsulation mode (JS33030). The receiver may select the encapsulation mode using the above-described initialization parameter.

The receiver determines whether encapsulation is enabled (JS33040). The receiver may determine whether encapsulation is enabled, using the above-described initialization parameter in this procedure.

Generally, since a header compression scheme is applied after the encapsulation procedure, if an encapsulation mode is disabled, the receiver may determine that a header compression mode is disabled (JS34100). In this case, since it is not necessary for the receiver to proceed to the initialization procedure any more, the receiver may immediately transmit data to another layer or transition to a data processing procedure.

The receiver selects a header compression mode (JS33050) when the encapsulation mode is enabled. Upon selecting the header compression mode, the receiver may determine a header compression scheme applied to a packet, using the above-described initialization parameter.

The receiver determines whether header compression is enabled (JS33060). If header compression is disabled, the receiver may immediately transmit data or transition to the data processing procedure.

If header compression is enabled, the receiver selects a packet stream reconfiguration mode and/or a context transmission mode (JS33070 and JS32080) with respect to a corresponding header compression scheme. The receiver may select respective modes using the above-described information in this procedure.

The receiver performs header compression initialization (JS33090). The receiver may use the above-described information in a procedure of performing header compression initialization. Then, the receiver may transmit data for another processing procedure or perform the data processing procedure.

FIG. 100 is a diagram illustrating a signaling format for transmitting an initialization parameter according to an embodiment of the present invention.

To actually transmit the above-described initialization parameter to a receiver, the broadcast system may transmit/receive corresponding information in the form of a descriptor. When multiple links operated in a link layer configured in the system are present, link_id information capable of identifying the respective links may be assigned and different parameters may be applied according to link_id information. For example, if a type of data transmitted to the link layer is an IP stream, when an IP address is not changed in the corresponding IP stream, configuration information may designate n IP address transmitted by a upper layer.

The link layer initialization descriptor for transmitting the initialization parameter according to an embodiment of the present invention may include descriptor_tag information, descriptor_length information, num_link information, link_id information, encapsulation_mode information, header_compression_mode information, packet_reconfiguration_mode information, context_transmission_mode information, max_cid information, large_cids information, num_profiles information, and/or profiles( ) information. A description of the above information is replaced with a description of the above-described information having a similar or identical name.

FIG. 101 is a diagram illustrating a signaling format for transmitting an initialization parameter according to another embodiment of the present invention.

The drawing illustrates a descriptor of another form to actually transmit the above-described initialization parameter to a receiver. In this embodiment, the above-described initial configuration information of header compression is excluded. When an additional header compression initialization procedure is performed in data processing of each link layer or an additional header compression parameter is given to a packet of each link layer, the descriptor configured in the same form as in this embodiment may be transmitted and received.

The link layer initialization descriptor for transmitting the initialization parameter according to another embodiment of the present invention may include descriptor_tag information, descriptor_length information, num_link information, link_id information, encapsulation_mode information, header_compression_mode information, packet_reconfiguration_mode information, and/or context_transmission_mode information. A description of the above information is replaced with a description of the above-described information having a similar or identical name.

FIG. 102 is a diagram illustrating a signaling format for transmitting an initialization parameter according to another embodiment of the present invention.

The drawing illustrates a descriptor of another form to actually transmit the above-described initialization parameter to a receiver. In this embodiment, a descriptor for transmitting the initialization parameter includes configuration information about a signaling transmission path without including initial configuration information of header compression.

The configuration parameter about the signaling transmission path may use a 4-bit mapping scheme as described above. When a broadcast system (or transmitter or a receiver) for processing a broadcast signal is changed, a link layer signaling transmission scheme or the contents of link layer signaling may differ. In this case, if the initialization parameter is transmitted in the same form as in this embodiment, the initialization parameter may be used even in the case of change of link layer signaling.

The link layer initialization descriptor for transmitting the initialization parameter according to another embodiment of the present invention may include descriptor_tag information, descriptor_length information, num_link information, signaling_path_configuration information, dedicated_DP_id information, link_id information, encapsulation_mode information, header_compression_mode information, packet_reconfiguration_mode information, and/or context_transmission_mode information.

When the link layer signaling information is transmitted through a dedicated DP, dedicated_DP_id information is information identifying the corresponding DP. When the dedicated DP is determined as a path for transmitting the signaling information in signaling path configuration, DP_id may be designated to include DP_id information in the descriptor for transmitting the initialization parameter.

A description of the above information contained in the descriptor is replaced with a description of the above-described information having a similar or identical name.

FIG. 103 is a diagram illustrating a receiver according to an embodiment of the present invention.

The receiver according to an embodiment of the present invention may include a tuner JS21010, an ADC JS21020, a demodulator JS21030, a channel synchronizer & equalizer JS21040, a channel decoder JS21050, an L1 signaling parser JS21060, a signaling controller JS21070, a baseband controller JS21080, a link layer interface JS21090, an L2 signaling parser JS21100, packet header recovery JS21110, an IP packet filter JS21120, a common protocol stack processor JS21130, an SSC processing buffer and parser JS21140, a service map database (DB) JS21150, a service guide (SG) processor JS21160, a SG DB JS21170, an AV service controller JS21180, a demultiplexer JS21190, a video decoder JS21200, a video renderer JS21210, an audio decoder JS21220, an audio renderer JS21230, a network switch JS21240, an IP packet filter JS21250, a TCP/IP stack processor JS21260, a data service controller JS21270, and/or a system processor JS21280.

The tuner JS21010 receives a broadcast signal.

When a broadcast signal is an analog signal, the ADC JS21020 converts the broadcast signal to a digital signal.

The demodulator JS21030 demodulates the broadcast signal.

The channel synchronizer & equalizer JS21040 performs channel synchronization and/or equalization.

The channel decoder JS21050 decodes a channel in the broadcast signal.

The L1 signaling parser JS21060 parses L1 signaling information from the broadcast signal. The L1 signaling information may correspond to physical layer signaling information. The L1 signaling information may include a transmission parameter.

The signaling controller JS21070 processes the signaling information or the broadcast receiver transmits the signaling information to an apparatus that requires the corresponding signaling information.

The baseband controller JS21080 controls processing of the broadcast signal in a baseband. The baseband controller JS21080 may perform processing in the physical layer on the broadcast signal using the L1 signaling information. When a connection relation between the baseband controller JS21080 and other apparatuses is not indicated, the baseband controller JS21080 may transmit the processed broadcast signal or broadcast data to another apparatus in the receiver.

The link layer interface JS21090 accesses the link layer packet and acquires the link layer packet.

The L2 signaling parser JS21100 parses L2 signaling information. The L2 signaling information may correspond to information included in the aforementioned link layer signaling packet.

When header compression is applied to a packet of a upper layer (e.g., an IP packet) than a link layer, the packet header recovery JS21110 performs header decompression on the packet. Here, the packet header recovery JS21110 may restore a header of the packet of the upper layer using information for identification of whether the aforementioned header compression is applied.

The IP packet filter JS21120 filters the IP packet transmitted to a specific IP address and/or UDP number. The IP packet transmitted to the specific IP address and/or UDP number may include signaling information transmitted through the aforementioned dedicated channel. The IP packet transmitted to the specific IP address and/or UDP number may include the aforementioned FIC, FIT, EAT, and/or emergency alert message (EAM).

The common protocol stack processor JS21130 processes data according to a protocol of each layer. For example, the common protocol stack processor JS21130 decodes or parses the corresponding IP packet according to a protocol of an IP layer and/or a upper layer than the IP layer.

The SSC processing buffer and parser JS21140 stores or parses signaling information transmitted to a service signaling channel (SSC). The specific IP packet may be designated as an SSC and the SSC may include information for acquisition of a service, attribute information included in the service, DVB-SI information, and/or PSI/PSIP information.

The service map DB JS21150 stores a service map table. The service map table includes attribute information about a broadcast service. The service map table may be included in the SSC and transmitted.

The SG processor JS21160 parses or decodes a service guide.

The SG DB JS21170 stores the service guide.

The AV service controller JS21180 performs overall control for acquisition of broadcast AV data.

The demultiplexer JS21190 divides broadcast data into video data and audio data.

The video decoder JS21200 decodes video data.

The video renderer JS21210 generates video provided to a user using the decoded video data.

The audio decoder JS21220 decodes audio data.

The audio renderer JS21230 generates audio provided to the user using the decoded audio data.

The network switch JS21240 controls an interface with other networks except for a broadcast network. For example, the network switch JS21240 may access an IP network and may directly receive an IP packet.

The IP packet filter JS21250 filters an IP packet having a specific IP address and/or a UDP number.

TCP/IP stack processor JS21260 decapsulates an IP packet according to a protocol of TCP/IP.

The data service controller JS21270 controls processing of a data service.

The system processor JS21280 performs overall control on the receiver.

FIG. 104 illustrates a layer structure when dedicated channels are present according to an embodiment of the present invention.

Data transmitted over a dedicated channel may not be an IP packet stream. Accordingly, application of a protocol structure different from IP based protocol structures may be needed. Data transmitted over the dedicated channel may correspond to data for a specific purpose. In the dedicated channel, various types of data may not coexist. In this case, the meaning of data becomes clear immediately after a receiver decodes the data in a physical layer in many cases.

In the above situation, data transmitted over the dedicated channel may not need to be processed according to the aforementioned protocol structures (for general broadcast data). That is, all processes for data transmitted over the dedicated channel may be completed in a physical layer and/or a link layer and information included in the data may be used.

In a broadcast system, data transmitted over a dedicated channel may be data for signaling (signaling information), and the data for signaling (signaling data) may be directly transmitted over the dedicated channel without being carried by an IP stream. In this case, a receiver may acquire the data transmitted over the dedicated channel more rapidly than data carried by an IP stream.

Referring to the shown protocol structure, dedicated channels may be configured in the physical layer. The figure illustrates a protocol structure related to processing of broadcast data in this case.

A part that conforms to a generic protocol structure may be referred to as a generic part and a part that conforms to a protocol part for processing dedicated channels may be referred to as a dedicated part in the present invention. However, the present invention is not limited thereto. Description of processing of broadcast data through the protocol structure in the generic part may be complemented by the above description of the specification.

Information (dedicated information A, dedicated information B and/or dedicated information C) may be transmitted through the dedicated part and delivered from the outside of the link layer or generated inside of the link layer. The dedicated part may include one or more dedicated channels. Processing of data transmitted over a dedicated channel may be performed in various manners in the dedicated part.

Dedicated information delivered to the link layer from the outside may be collected through a signaling generation and control module in the link layer and processed into formats adapted to dedicated channels. A processing format of dedicated information transmitted over a dedicated channel may be referred to as a dedicated format. Each dedicated format may include each piece of dedicated information.

Data (signaling data) transmitted through the generic part may be processed into packet formats of the protocol of the link layer as necessary. In this process, the signaling data transmitted through the generic part and signaling data transmitted through the dedicated part may be multiplexed. That is, the signaling generation and control module may have a function for performing multiplexing.

When dedicated information can be directly processed in a dedicated channel, processing of data in the link layer may be performed in the transparent mode (bypass mode), as described above. Data processing may be performed in the transparent mode for some or all dedicated channels. Data processing in the dedicated part may be performed in the transparent mode and data processing in the generic part may be performed in the normal mode. Alternatively, processing of normal data in the generic part may be performed in the transparent mode and processing of signaling data transmitted through the generic part and processing of data in the dedicated part may be performed in the normal mode.

When a dedicated channel is configured and dedicated information is transmitted according to an embodiment of the present invention, a receiver can rapidly access necessary information (dedicated information) since processing according to each protocol defined in a broadcast system need not be performed.

Description of data processing in the generic part and/or higher layers of the link layer in the figure may be replaced by the above description.

FIG. 105 illustrates a layer structure when dedicated channels are present according to another embodiment of the present invention.

According to another embodiment of the present invention, a structure in which link layer processing is performed in the transparent mode for part of dedicated channels may be present. That is, processing of data transmitted over part of dedicated channels in the link layer may be omitted. For example, dedicated information A may be directly transmitted over a dedicated channel without being configured in a separate dedicated format. This transmission structure may be used when dedicated information A conforms to a known structure in a broadcast system. Examples of the structure known in the broadcast system may include a section table and/or a descriptor.

In an embodiment of the present invention, when dedicated information corresponds to signaling data, up to a part in which the signaling data is generated may be regarded as the range of the link layer in a broad sense. That is, the dedicated information may be generated in the link layer.

FIG. 106 illustrates a layer structure when dedicated channels are independently present according to an embodiment of the present invention.

The figure illustrates a protocol structure for processing broadcast data when a signaling generation and control module is not configured in the link layer. Dedicated information may be processed into a dedicated format and transmitted over a dedicated channel.

Signaling information, which is not transmitted over a dedicated channel, may be processed into a link layer packet and transmitted through a data pipe.

The dedicated part may have one or more protocol structures adapted to respective dedicated channels. In this structure, the link layer does not require an additional control module, and thus a relatively simple system may be configured.

In the present embodiment, dedicated information A, dedicated information B and dedicated information C may be processed through different protocols or the same protocol. For example, dedicated information A, dedicated information B and dedicated information C may be processed into different formats.

According to the present invention, an entity that generates dedicated information may transmit data when necessary without considering scheduling of the physical layer and the link layer. Data may be processed in the transparent mode (or bypass mode) for some or all dedicated channels as necessary.

Description of data processing in the generic part and/or higher layers of the link layer in the figure may be replaced by the above description.

FIG. 107 illustrates a layer structure when dedicated channels are independently present according to another embodiment of the present invention.

In the aforementioned embodiment describing the layer structure when dedicated channels are independently present, processing in the link layer may be performed in the transparent mode for part of the dedicated channels. Referring to the figure, dedicated information A may be directly transmitted over a dedicated channel without being processed into a separate format. This transmission structure may be used when dedicated information A conforms to a structure known in a broadcast system. Examples of the structure known in the broadcast system include a section table and/or a descriptor.

In an embodiment of the present invention, when dedicated information corresponds to signaling data, up to a part in which the signaling data is generated may be regarded as the range of the link layer in a broad sense. That is, the dedicated information may be generated in the link layer.

FIG. 108 illustrates a layer structure when a dedicated channel delivers specific data according to an embodiment of the present invention.

A fast information channel (FIC) for bootstrapping service level signaling or scanning services and/or an emergency alert channel (EAC) including information for emergency alert may be delivered through a dedicated channel. Data transmitted through the FIC may be called a fast information table (FIT) or a service list table (SLT) and data transmitted through the EAC may be called an emergency alert table (EAT).

Description of FIT and information that can be included in the FIT is replaced by the above description. The FIT may be directly generated and transmitted by a broadcaster or generated by collecting information in the link layer. When the FIT is directly generated and transmitted by a broadcaster, information for identifying the broadcaster may be included in the FIT. When the FIT is generated by collecting information in the link layer, information used to scan services provided by all broadcasters may be collected to generate the FIT.

When the FIT is generated and transmitted by a broadcaster, the link layer operates in the transparent mode such that the FIT may be directly transmitted to the FIC. When the FIT is generated by combining information of a transmitter, the operation range of the link layer may include generation of the FIT and configuration of the information in the form of a table.

Description of the EAT and information that can be included in the EAT is replaced by the above description. Regarding the EAC, when an entity (e.g., IPAWS) that manages an emergency alert message delivers the message to a broadcaster, an EAT associated with the message may be generated and transmitted through the EAC. In this case, generation of a signaling table based on the emergency alert message may be included in the operation range of the link layer.

Signaling information, as described above, which is generated to process IP header compression, may be transmitted through a data pipe instead of a dedicated channel. Here, processing for transmitting the signaling information may conform to the protocol of the generic part and may be transmitted in the form of a general packet (e.g. link layer packet).

FIG. 109 illustrates a format (or dedicated format) of data transmitted through a dedicated channel according to an embodiment of the present invention.

When dedicated information transmitted over a dedicated channel is not suitable for direct transmission through the dedicated channel or requires an additional function, the link layer may encapsulate the dedicated information into data in a format that can be processed in the physical layer. In this case, the aforementioned packet structures according to the protocol of the generic part supported by the link layer may be used. The dedicated channel does not require a function supported by the structure of a packet transmitted through the generic part in many cases. In this case, the dedicated information may be processed into a format adapted to the dedicated channel.

For example, the dedicated information may be processed into a dedicated format and transmitted over the dedicated channel in the following cases.

1) When the size of data that can be transmitted through the dedicated channel does not correspond to the size of the dedicated information to be delivered

2) When the dedicated information is configured in a data format (e.g. XML) that requires an additional parser, instead of a table format

3) When it is necessary to check the version of the information, before parsing relevant data, to determine whether to process the information

4) When an error in the dedicated information needs to be detected

When the dedicated information needs to be processed into the dedicated format, as described above, the dedicated format may have the format shown in the figure. A header including part of fields may be separately configured within a range that meets the purpose of each dedicated channel, and the number of bits assigned to each of the fields may be changed.

The dedicated format according to an embodiment of the present invention may include a length field, a data_version field, a payload_format field (or data_format field), a stuffing_flag field, a CRC field, a payload_data_bytes( ) element, a stuffing_length field and/or a stuffing_bytes field.

The length field indicates the length of data included in a payload. The length field may indicate the data length in bytes.

The data_version field indicates the version of information of the data. A receiver may check whether the information has been received or is new information using the version information and determine whether to use the information using the same.

The data_format field indicates the format of information constituting dedicated information. For example, a data_format field value of “000” may indicate that the dedicated information is transmitted in a table format, and a data_format field value of “001” may indicate that the dedicated information is transmitted in a descriptor format. A data_format field value of “010” may indicate that the dedicated information is transmitted in a binary format instead of the table or descriptor format and a data_format field value of “011” may indicate that the dedicated information is transmitted in the XML format.

The stuffing_flag field may identify a stuffing byte. The stuffing byte may be added to adjust the length of necessary data when a dedicated channel is greater than dedicated information.

The stuffing_length field may indicate the length of the stuffing_bytes field.

The stuffing_bytes field may be filled with stuffing bytes corresponding to the size indicated by the stuffing_length field. The stuffing_bytes field may indicate the size of stuffing bytes.

The CRC field may include information for checking an error with respect to data to be transmitted over a dedicated channel. The CRC field may be calculated using information (or field) included in dedicated information. A receiver may ignore received information upon determining that an error is detected from the information using the CRC field.

FIG. 110 illustrates dedicated channel configuration information for signaling information about a dedicated channel according to an embodiment of the present invention.

The aforementioned operation in the transparent mode or normal mode for a dedicated channel may be determined when the dedicated channel is designed and is not changed during system operation, in general. However, since a plurality of transmission systems and reception systems are present in a broadcast system, processing modes for dedicated channels may need to be flexibly controlled. For flexible system configuration, operation modes may be changed or reconfigured and signaling information may be used to provide information on the operation modes to a receiving side. The signaling information may be transmitted in physical layer signaling (L1 signaling; transmission parameter) or transmitted over a specific dedicated channel. The signaling information may be included in a table or a descriptor used by the broadcast system. That is, the signaling information may be included as part of signaling information described in the specification.

The dedicated channel configuration information may include a num_dedicated_channel field, a dedicated_channel_id field and/or an operation_mode field.

The num_dedicated_channel field may indicate the number of dedicated channels included in the physical layer.

The dedicated_channel_id field may correspond to an identifier for identifying a dedicated channel. A dedicated channel may be assigned an identifier (id) as necessary.

The operation_mode field may indicate a processing mode for a dedicated channel. For example, an operation_mode field value of “0000” may indicate that the dedicated channel is processed in the normal mode. An operation_mode field value of “1111” may indicate that the dedicated channel is processed in the transparent mode (or bypass mode). Operation_mode field values of “0001” to “1110” may be reserved for future use.

FIG. 111 is a diagram illustrating a layered signaling structure according to an embodiment of the present invention.

Prior to description of the layered signaling structure of a broadcast system according to the present invention, terms used in the present invention may be defined as follows.

The 3GPP may indicate 3rd Generation Partnership Project.

The ALC may indicate Asynchronous Layered Coding. A detailed description of a related protocol may refer to content of the RFC 5775 document such as layered coding transport (LCT).

The Broadband Stream may correspond to an RF channel. The RF channel may be defined as a center carrier frequency of a specific bandwidth.

The DASH may indicate Dynamic Adaptive Streaming over HTTP and a detailed description thereof refers to content of the ISO/IEC 23009-1 document.

The eMBMS may indicate evolved Multimedia Broadcast/Multicast Service. The eMBMS may be a technology of describing content of cellular mobile broadcast of a service through an LTE network.

The FIT may indicate Fast Information Table. The FIT may generate a basic service list or include an ROUTE session for transmitting the SLS and information for bootstrapping discovery of an LCT channel.

The LCT may indicate Layered Coding Transport. The LCT may be a building block technology defined in the RFC 5651 document and may provide a stream delivery protocol and transport level support for supporting reliable content delivery.

The LLS may indicate Link Layer Signaling. The LLS may correspond to signaling information transmitted by a payload of a packet of a second layer prior to a third layer (e.g., an IP layer).

The MMTP may indicate MPEG Multimedia Transport. Content of the MMTP may refer to content of the ISO/IEC 23008-1 document.

The MPD may indicate Media Presentation Description. The MPD may include a formulated description of the DASH media presentation for providing a streaming service. The MPD may be included in a fragment of SLS to transmit a streaming service.

The MPU may indicate Media Processing Unit. A description related to the MPU may refer to content of the ISO/IEC 23008-1 document.

The PLP may indicate Physical Layer Pipe. The PLP may be a portion that is used to transmit service metadata such as service signaling and/or a content component of an ATSC3.0 service and corresponds to a transmission capacity provided by a broadcast stream and may correspond to a combination of data associated by a specific modulation and coding parameter.

The ROUTE may indicate Real-Time Object delivery Over Unidirectional Transport. The ROUTE may define a technology for enabling real time streaming to provide a service via file-based transmission.

The SLS may indicate Service Layer Signaling. The SLS may include information required to discover and acquire an ATSC3.0 service and content components thereof. The SLS data may be transmitted through a third layer (e.g., an IP packet).

The S-TSID may indicate Service-based Transport Session Instance Description. The S-TSID may correspond to a fragment of SLS metadata defined in the form of XML. The S-TSID may include session description information for transport sessions for transmitting content components included in the ATSC service. The S-TSID may include or refer to objects transmitted through associated transport session and/or description information of delivery of object flow.

The TOI may indicate Transmission Object Identifier. The TOI may be transmitted by an LCT header and may correspond to a unique identifier of a delivery object transmitted in the ALC/LCT session.

The TSI may indicate Transmission Session Identifier. The TSI may be an identifier of an ALC/LCT transport session within a range of a TSI value and an IP address of a sender.

The USBD/USD may indicate User Service Bundle Description/User Service Description. The USBD may correspond to the XML form of SLS metadata fragment. The USBD may function as an entry point for access to a fragment (e.g., S-TSID, MPD, and/or MMTP) included in other SLS. That is, the USBD may include information required to access to the fragment included in the SLS. The USBD may identify an ATSC3.0 service and include basic information on a service, such as a service name or a service language. Each USBD may include information on one service represented by userServiceDescription (USD).

The XML Diff may indicate a difference between two XML files. The XML Diff may corresponds to XML signaling template and/or XML signaling instance that are generated by the sender and transmitted to the receiver. To acquire the signaling instance, the receiver may apply the XML Diff to local copy of the template owned by the receiver. The XML Diff mechanism may be a method that replaces a compression tool (e.g., Gzip) used to compress SLS data transmitted through a broadcast network and may be provided by a broadcast system.

The layered signaling structure of the broadcast system according to the present embodiment may support streaming using two or more different service delivery methods. That is, the proposed layered signaling structure may provide integrated signaling for service delivery of DASH through ROUTE and service delivery of MPU through MMTP.

As described above, the layered signaling structure may be divided into Low Level Signaling and Service Level Signaling. The Low Level Signaling may be transmitted via Link Layer Signaling. The Low Level Signaling may include the aforementioned FIT (or SLT).

The SLS may be transmitted through a broadcast network and, in this case, may be processed according to a protocol of ROUTE/UDP/IP. The SLS may be transmitted through a broadcast network and, in this case, may be processed according to a protocol of HTTP(s)/TCP/IP.

The SLS may be a signaling structure (or fragment) including information for signaling of a general service and may include USBD and/or S-TSID.

The SLS may be a signaling structure (or fragment) including signaling information required for content streaming and may include MPD.

The SLS may further include a signaling structure (or fragment) for providing a service (content or an event) executed based on an application.

Referring to the drawing, when a service is provided based on ROUTE through a broadcast network, the receiver may access the SLS by using information of the LLS and acquire DASH representation (or component) for a service by using the information of the MPD included in the SLS.

When a service is provided based on MMT through a broadcast network, the receiver may access the SLS by using information of the LLS, acquire MMT signaling message by using the information of the SLS, and acquire a packet for transmitting an MMT asset (component) for a service by using the information included in the MMT signaling message.

When the layered signaling structure according to the present invention is used, integrated signaling for ROUTE/DASH and MMTP/MPU streaming transmission may be provided.

When the layered signaling structure is used, integrated signaling for hybrid service transmissions through a broadcast network and a broadband network may be provided.

When the layered signaling structure is used, the conventionally used 3DPP eMBMS standard and the next-generation broadcast standard may be connected to obtain connectivity between heterogeneous devices.

When the layered signaling structure is used, entire signaling data may be effectively transmitted/received.

When the layered signaling structure is used, a receiving side may acquire a desired fragment via simple filtering on broadcast signaling.

When the layered signaling structure is used, two or more compression options for signaling data may be freely used (Gzip and/or XML Diff).

FIG. 112 is a diagram illustrating a transmission path of an FIT according to an embodiment of the present invention.

A broadcast receiver may begin access a service from the FIT (or SLT) in a broadcast emission. The FIT may include the aforementioned information item and provide information required for rapid channel scan to write a list of services to be received by the receiver. The FIT may include information (bootstrap information) required to access to the SLS. The bootstrap information may include source IP address information of a packet for transmitting the SLS, destination IP address information, destination port information, TSI information of an LCT session for transmitting the SLS, and/or ID information for PLP for transmitting the SLS. However, the PLP ID information that is information for identifying the PLP for transmitting the SLS may be included in the aforementioned first layer signaling (i.e., physical layer signaling or L1 signaling).

The FIT may include ID information for identifying one broadcast stream and the ID information for identifying the broadcast stream may be used as information for identifying a broadcaster. That is, the FIT may be separately provided for each broadcaster.

The FIT may include a service loop including information for each of services provided through a broadcast stream identified by each ID information item.

The service loop may include service ID information for uniquely identifying a service in a range of a broadcast area, short name information indicating a shot name of a service, provider ID information (e.g., information used to identify a broadcaster that uses a portion of a broadcast stream when a broadcast stream is shared by a plurality of broadcasters) for identifying a provider of each service, and/or bootstrap information as information for acquiring SLS for each service.

A detailed description of the information items included in the FIT has been given or will replace a description to be described later.

Referring to the drawing, (1) a method of transmitting the FIT in the PLP for transmitting components included in a service, (2) a method of defining a dedicated channel for transmission of the FIT in a physical layer and transmitting the FIT through a corresponding channel, or (3) a method of defining a PLP for transmitting main data and signaling such as FIT and identifying the corresponding PLP may be provided and the FIT may be transmitted to the corresponding PLP.

FIG. 113 is a diagram for bootstrapping SLS by using FIT according to an embodiment of the present invention.

A receiver may acquire a FIT transmitted using the aforementioned method through an RF channel (a physical layer signal). The drawing illustrates the case in which an LLS (FIT) is transmitted through a dedicated channel in a broadcast signal.

The receiver may search for a region of a broadcast signal for transmitting the SLS of a service that the receiver intends to access by using Service ID information, Service Category information, SLS source IP address information, SLS destination IP address, SLS destination port number information, SLS PLP ID information, and/or SLS TSI information, which are included in the FIT. The SLS may be transmitted to a ROUTE session. That is, the receiver may access a specific region in a ROUTE session for transmitting the SLS to acquire the SLS by using the above information included in the FIT.

The receiver may acquire data and information required to express a service by using USBD, MPD, and/or S-TSID, which are included in the acquired SLS.

The SLS may be defined for each service level and may include information for describing access and attribute of the service. For example, information included in the SLS may include information for listing content components included in a service, information required to acquire corresponding components, and information for identifying performance required to the receiver to express a corresponding component or service.

The SLS may be defined in the form of XML. To transmit the SLS, a dedicated LCT session may be defined.

The SLS may further include a fragment including signaling information required to provide an application-based service in addition to a USBD fragment, an MPD fragment, and an S-TSID fragment. The SLS may provide a delivery session description information including information for access to a ROUTE session and/or an MMTP session as described above.

FIG. 114 is a diagram illustrating extension of 3DPP MBMS signaling for a broadcast system according to an embodiment of the present invention.

In a signaling structure for a broadcast system, an SLS may include a USBD fragment and the USBD fragment may use the form defined in the 3GPP MBMS. In this case, the USBD defined in the 3GPP MBMS needs to further include signaling information required for the broadcast system.

The information that needs to be further included for the broadcast system may include @atsc:serviceId information, @atsc:sTsidUri information, @atsc:fullMpdUri information, <atsc:capabilityCode> element, <atsc:broadcastAppService> element, <basePattern> element, <atsc:unicastAppService> element, and/or <basePattern> element.

The @atsc:serviceId information may be information for identifying a broadcast service.

The @atsc:sTsidUri information may be information for connecting S-TSID in the USBD. The @atsc:sTsidUri information may be URI information on a region in which the S-TSID is transmitted.

The @atsc:fullMpdUri information may be information for connection of MPD in the USBD. The @atsc:fullMpdUri information may be URI information of a region in which the MPD is transmitted.

The <atsc:capabilityCode> element may include information for identifying performance required by a receiver to enable meaningful expression of a service or a component.

The <atsc:broadcastAppService> element may include signaling information of an application-based service transmitted through a broadcast network and the <basePattern> element included in a lower portion of the element may indicate a base pattern of a URI required to acquire the corresponding application-based service.

The <atsc:unicastAppService> element may include signaling information of an application-based service transmitted through a unicast network and the <basePattern> element included in a lower portion of the element may indicate a base pattern of a URI required to acquire the corresponding application-based service.

The @atsc:serviceId information may have 16 bits and may be used for a link with a service ID included in the FIT.

The USD may include a service level description that is not capable of being included in the FIT. Since the FIT has a limited capacity, the FIT may not be capable of including service level signaling information and, thus, the service level signaling information that is not capable of being included in the FIT may be included in the USD. The information may include information indicating a service name represented by different languages, information for identifying whether each service component is transmitted through a broadcast network or a broadband network (or a method of transmitting a component may be determined by the basePatten element used as a matching pattern corresponding to a segment URL requested by a DASH client), information for identifying performance required by the receiver, content advisory related information, caption description information, and/or information required to be extended for an ATSC3.0 broadcast system.

The S-TSID may include entire session description of delivery session(s) for transmitting a content component of an ATSC service.

To transmit a linear service that does not include application-based enhancement through a broadcast network, the S-TSID may include information (when service components are transmitted through an ROUTE) for describing an LCT session and/or information (when service components are transmitted through an MMTP) for describing an MMTP session. The application-based enhancement may be provided alone as an event, content, and/or a service which are provided based on an application or may be used with a linear service as an additional service/content/event for a linear service.

When service components are streaming through an ROUTE, the S-TSID may include file metadata for transmitting an object or object flow transmitted through an LCT session of a service and/or additional information of content components and a payload format which are transmitted through LCT sessions.

The SLS may be transmitted through an ALC/LCT session of an ROUTE session. A fragment (service signaling fragment) included in the SLS may be updated in the form of metadata envelope as defined in the 3GPP MBMS and this form may include identification information for the fragment, version information, update information, and/or compression information. The receiver may use a filtering scheme that employs structured TOI of an LCT packet including a filter parameter for an effective packet combination.

The service signaling fragment may be compressed using Gzip and/or a template/Diff based method. When the template/Diff-based method is used, a size of signaling may be reduced and only a portion of signaling is capable of being changed such as update, thereby obtaining efficiency in data transmission and data processing of a receiver, as described above.

When the signaling fragment is compressed via the template/Diff-based compression, a signaling template may be pre-shared by a transmitting end and a receiving end. In this case, signaling instance and template that are required to be transmitted from a transmitting end may be compared to generate Diff. The transmitting end may transmit the Diff to a client. A receiving end may apply the Diff to the template to acquire the signaling instance. In this manner, when a difference between the template and a complete fragment is very small, a broadcast system may be effectively operated in data transmission and data processing compared with a compression method such as Gzip.

FIG. 115 is a diagram illustrating protocol stack of a broadcast system according to an embodiment of the present invention.

An ATSC3.0 service may be transmitted using three functional layers. These may be a physical layer, a delivery layer, and a service management layer. The physical layer may provide a mechanism for transmitting signaling transmitted through a broadcast physical layer and/or a broadband physical layer, service announcement, and IP packets. The delivery layer may provide an object and object flow delivery function. That is, in the delivery layer, an ROUTE protocol through a broadcast physical layer and an operation in UDP/IP multicast may be performed and an HTTP protocol through a broadband physical layer and a TCP/IP unicast operation may be performed. The service management layer may permit any type of service such as a linear TV or an HTML5 application to perform transmission through a delivery layer and a physical layer.

The service signaling may provide information for service discovery and description. The service signaling may include two functional components. One of these may be bootstrap signaling (FIT—Fast Information Table or SLT—Service List Table) and the other one may be service layer signaling (SLS). The service signaling may include information required to discover and acquire user services. The FIT may permit the receiver to generate a basic service list and to perform bootstrapping for discovery of the SLS for each ATSC3.0 service. The FIT may be transmitted in a link layer or an upper layer thereof or may be transmitted for each frame of a physical layer for rapid acquisition. The SLS may enable the receiver to discover and access an ATSC3.0 service and content components thereof. When the SLS is transmitted through a broadcast network, the SLS may be transmitted by ROUTE/UDP/IP included in one of LCT delivery sessions including a ROUTE session with a carousel rate appropriate for rapid channel subscription and support switching. When the SLS is transmitted through a broadcast network, the SLS may be transmitted through HTTP(s)/TCP/IP.

FIG. 116 illustrates a correlation of entities of a service management layer, a delivery layer, and a physical layer, according to an embodiment of the present invention.

In a broadcast system according to the present invention, ROUTE/LCT sessions and/or MMTP sessions may be present to transmit content components of an ATSC3.0 service.

To transmit a linear service that is not present with application-based enhancement through a broadcast network, content components included in a service may be transmitted through one or more ROUTE/LCT sessions or one or more MMTP sessions.

To transmit a linear service including application-based enhancement through a broadcast network, content components of a service may be transmitted through one or more ROUTE/LCT session and 0 or more MMTP sessions. That is, in this case, some of content components constituting one service may be transmitted through an ROUTE/LCT session and other some of the content components may be transmitted through an MMTP session. For example, content components included in the application-based enhancement may be transmitted through only a ROUTE and, thus, when even a service that basically applies the MMTP includes application-based enhancement, the ROUTE frequently needs to be used to transmit some components. However, for streaming of media components in the same service, use of both the MMTP and the ROUTE may not be permitted.

To transmit an application service through a broadcast network, content components included in the service may be transmitted through one or more ROUTE/LCT sessions.

Each ROUTE session may include one or more LCT session for transmitting some or all of content components for making the ATSC3.0 service. With regard to streamlining service transmission, one LCT session may transmit one separate component of a user service such as audio, video, or closed caption stream. The streaming media may be formatted and transmitted in the form of DASH segments of MPEG DASH.

Each MMTP session may transmit some or all of content components or include one or more MMTP packet flows for transmitting an MMTP signaling message. One MMTP packet flow may transmit a component of MPU form of MMT or a MMT signaling message. To transmit an NRT user service or system metadata, the LCT session may transmit a file-based content item. Files included in the content may include media components of continuous or time-based or discrete or non-time-based NRT service or include media data such as service signaling or ESG fragment.

A broadcast stream may be a concept for an RF channel and may be defined as the term of a center carrier frequency in a specific bandwidth. The broadcast stream may be identified by a geographical area and a frequency. With pair between a geographical area and frequency information, a broadcast stream ID of the pair may be defined and managed by administrative power. The PLP may correspond to a portion of an RF channel. Each PLP may have specific modulation and coding parameters. The PLP may be identified by a unique PLP ID in a broadcast stream to which the PLP belongs.

Each service may be identified by two types of service identifiers. One may be a compact type of service identifier that is used in an FIT and is unique only in a broadcast area or a broadcast stream and the other one may be globally unique form of service identifier used in the SLS and the ESG. One ROUTE session may be identified by a source IP address, a destination IP address, and a destination port number. One LCT session (which is related to a service component for transmitting the same) may be identified by a unique transport session identifier (TSI) in a range of an ROUTE session to which the LCT session belongs.

Characteristics common to LCT sessions and unique specific characteristics in each LCT session may be given in a ROUTE signaling structure called service-based transport session instance description (S-TSID). The S-TSID may be a portion of service level signaling. Each LCT session may be transmitted through one PLP. Different LCT sessions of one ROUTE session may be included in different PLPs or not. Characteristics described in the S-TSID may include a descriptor for transmission of a TSI value, a PLP ID for each LCT session, and an object/file, and/or an application layer FEC parameter.

One MMTP session may be identified by a destination IP address and a destination port number. One MMTP packet flow (which is associated with service components for transmitting the same) may be identified by a unique packet_id in a range of an MMTP session including the flow. Characteristics common to each MMTP packet flow and specific characteristics of the MMTP packet flow may be given by the S-TSID. Characteristics for each MMTP session may be given by an MMT signaling message transmitted in the MMTP session. Each MMTP packet flow may be transmitted through one PLP. Different MMTP packet flows of one MMTP session may be transmitted through different MMTP packet flows or not. Characteristics described in the MMT signaling message may include a packet_id value and/or a PLP ID for each MMTP packet flow.

Information for identifying a PLP described as being included in the service level signaling or the FIT (or SLT) may be defined in signaling of a link layer. In this case, upon acquiring signaling transmitted through a link layer, a receiver may identify or access IT (or SLT), service level signaling, or a PLP associated with a component.

FIG. 117 is a diagram illustrating a signaling structure of a broadcast system according to an embodiment of the present invention.

Signaling information transmitted through a payload of a link layer packet (or an upper layer thereof) or content of a dedicated channel may be referred to as link layer signaling (LLS) or low level signaling (LLS). The aforementioned FIT (or which is referred to as a service list table (SLT)) may be classified as an LLS. The FIT may be functionally similar to a program association table (PAT) defined in the MPEG-2 system or a fast information channel (FIC) defined in or the ATSC-MH. Upon receiving a transmitted broadcast stream, the receiver may process data or a service from the FIT. The FIT may support the receiver to rapidly scan a channel. That is, the FIT may include information required to generate a list of all receivable services. The information may include information such as a channel name and/or a channel number, and so on. In addition, the FIT may include bootstrap information to permit the receiver to discover an SLS for each service. The bootstrap information may include TSI information of an LCT session for transmitting the SLS, a source IP address of an ROUTE session, a destination IP address, and/or a destination port number information.

The SLS for each service may describe attribute of a service. For example, the SLS may include information about where a list of components included in a service and the corresponding component are obtained and/or information about performance required by a receiver for meaningful expression of the corresponding service. In a ROUTE/DASH system, the SLS may include user service bundle description (USBD), S-TSID, and media presentation description (DASH MPD). The USBD may be based on a service description metadata fragment having the same term defined in the 3GPP-MBMS, may have an extended form of the corresponding metadata fragment to support a function of an ATSC3.0 system, and may be defined to have compatibility with the 3GPP-MBMS in the future. A description of information included in the USBD will be replaced with the aforementioned description of the USBD (or USD) or a description of the USBD (or USD) which will be described below.

Service signaling may concentrate on basic attribute of a service itself. In particular, the service signaling may concentrate on content of attribute required to acquire a service. A program intended for characteristics and a viewer of a service may be represented as service announcement or ESG data.

When a receiver has service signaling divided for each service, the receiver may permit an appropriate SLS for an interested service without need for parsing an entire SLS transmitted in a broadcast stream.

Service signaling may also be transmitted through broadband and, in this case, the FIT may include a HTTP URL for a position where a service signaling file (a file including service signaling) is capable of being acquired.

When an even such as update occurs in SLS signaling, the corresponding event may be detected by a “SLS version” field included in the FIT. The updated signaling may be acquired through a broadcast network or a broadband network.

The drawing shows an embodiment in which bootstrap for acquisition of an SLS is performed using an LLS and the SLS is used to acquire service components transmitted through a ROUTE/LCT delivery session. The receiver may begin to acquire a FIT transmitted by a physical layer frame in a predetermined frequency band identified by a broadcast stream ID (BSID). With regard to each service identified by Service_id, SLS bootstrapping information—PLPID(#1), source IP address (sIP1), destination IP address (dIP1), destination port number (dPort1), and TSI (tsi-SLS) may be provided. The receiver may acquire SLS fragments transmitted through a PLP and an IP/UDP/LCT session. The fragments may include a USBD/USD fragment, an S-TSID fragment, and a MPD fragment. These may be fragments for transmitting metadata associated with one service. The USBD/USD fragment may describe characteristics of a service level and provide a URI connected to the S-TSID fragment and a URI connected to the MPD fragment. The S-TSID fragment may be associated with one service and may provide component acquisition information for providing mapping information between DASH representation included in the MPD and the TSI corresponding to a component of the corresponding service. The S-TSID may provide component acquisition information in the form of an ID of a PLP for transmitting a DASH segment associated with DASH representation, a TSI, and an associated DASH representation ID. The receiver may collect audio/video components of a service, begin buffering of DASH mediate segments, and perform an appropriate decoding procedure by using PLPID and TSI values.

A layered signaling structure including two separate S-TSID fragments for providing access information for LCT sessions for transmitting contents of one separate service will be described below.

Service signaling may provide bootstrap and discovery information for a current “on-the-air” broadcast service. The current “on-the-air” broadcast service may correspond to, for example, a Linear TV service. The ESG may provide user service announcement indicating a list of contents and available ATSC3.0 user services with detailed information including performance required by a device, content rating, and an expression schedule. The information may be required by an ESG client in the receiver to be expressed to a user to enable service or content selection or to determine whether a related service or content needs to be formed to be shown to the user. Connection between a service of the ESG and a service of the SLS may be performed by a service identifier. This may be a key for identifying service attributes in the ESG as well as a key for identifying service attributes including delivery related attributes in signaling, in particular.

Link layer signaling may be operated at an IP level or less. The receiver may be more rapidly acquired than IP level signaling (e.g., service layer signaling). The link layer signaling may be acquired prior to establishment of a session.

The object of link layer signaling is to effective delivery of information required for rapid channel scan and service acquisition. The information may mainly include information for connection between ATSC3.0 service layer signaling and PLPs. Link layer signaling may further include signaling related to emergency alert. The link layer signaling may be encapsulated through a protocol of a link layer and may correspond to signaling to be acquired when a protocol of a link layer is executed.

The link layer signaling may be referred to as low level signaling. Although the link layer signaling has been described as signaling that is capable of being acquired at a lower level than an IP level, when a dedicated channel for corresponding signaling is generated in a broadcast signal, the link layer signaling may be defined at an upper layer of an IP level. In this case, the receiver may previously access link layer signaling compared with service layer signaling by using an IP address and/or UDP port number allocated to a corresponding dedicated channel.

The service layer signaling (or which is also referred to as service level signaling) (SLS) may include a USBD and an S-TSID metadata fragment. The service signaling fragments may be applied to both a linear service and an application-based service. The USBD fragment may include a service identifier, device performance information, information for referring to other SLS fragments required to access a service and a media component included in the service, and/or metadata for permitting the receiver to determine a transmission mode (broadcast network transmission and/or broadband network transmission) of service components. The S-TSID fragment referred by the USBD may include a delivery session descriptor for one or more ROUTE/LCT sessions or MMTP sessions for transmitting media content components of one ATSC3.0 service and a description of delivery objects transmitted in LCT sessions.

A component (fragment) for signaling streaming content in the SLS may correspond to an MPD fragment. The MPD may be general streaming content and may be related to a linear service for transmission of DASH segments. The MPD fragment may be used to support application-based services and needs to be associated with content components of DASH format. The MPD may include information required to reproduce contents. The MPD may provide a resource identifier for separate media components of a linear or streaming service in the form of segment URL and provide context of resources identified in media presentation.

The application-based enhancement signaling may include information for transmission of application-based enhancement components such as an application logic file, an NRT media file, an on-demand content component, or a notification stream. The application may acquire NRT data through broadband connection.

For synchronization between services, components, or events, a sequence of accurate wall clock references may be transmitted by a physical layer.

The service signaling of a service may be transmitted in an ALC/LCT session of a ROUTE session. The service signaling fragment may be encapsulated in metadata envelope as defined in the 3DPP MBMS. This form of encapsulation may permit identification, versioning, and update of an included fragment. The metadata envelope and the included fragment may be compressed via Gzip. The receiver may use a template-based compression method.

The receiver may signal a type and version of a signaling fragment of a service layer signaling fragment and perform filtering of the signaling fragment. Prior to acquisition of the entire service layer signaling fragment from packets in this manner, a target LCT packet for transmitting an expected type of service layer signaling fragment may be rapidly filtered. This method may be performed by defining a TOI structure of an LCT header, which will be described below.

FIG. 118 is a diagram illustrating an FIT according to an embodiment of the present invention.

In the present invention, the FIT may be used as the term such as FIC, SLT, or low level signaling (LLS). Alternatively, the FIT may be defined as one signaling structure included in the LLS. In this case, partial information included in the FIT disclosed in an embodiment of the present invention may be included in the LLS. The LLS may correspond to signaling information transmitted through a payload of an IP packet having a well-known address/port in a broadcast system.

The illustrated FIT may correspond to a signaling structure for supporting broadcast service scan and acquisition in a receiver. To this end, the FIT may include sufficient information for expression of a meaningful service list to a user and sufficient information for supporting service selection through a channel number or up/down zapping. The FIT may include sufficient information to locate service layer signaling of service through a broadcast network or a broadcast network according to where signaling is available.

Broadcast service and/or content generated by one or more broadcaster may be transmitted in a specific frequency. In this case, to permit the receiver to rapidly and easily scan a broadcaster present in a corresponding frequency and/or a service of the corresponding broadcaster and/or content, information required during this procedure may be signaled through the FIT.

When the signaling structure proposed in the present invention is used, the receiver may perform scan and speed for acquiring a service by the receiver may be reduced. The illustrated FIT is described in syntax but information included in the FIT may be represented in other format such as XML.

In the present invention, a fast information table (FIT) may be transmitted through an information channel (FIC) as a separate channel in a physical layer transport frame. The FIT may be transmitted through a Common DP or the like, for transmitting information shared between data pipes of a physical layer. Information included in the FIT may be transmitted via a path for transmitting layer signaling defined in the link layer or link layer signaling. In addition, the FIT may be transmitted via a service signaling channel for transmitting service signaling, a transport session of an application layer, or the like.

The FIT according to an embodiment of the present invention may include FIT_protocol_version information, Broadcast_stream_id information, FIT_section_number information, total_FIT_section_number information, FIT_section_version information, FIT_section_length information, num_services information, service_id information, SLS_data_version information, service_category information, short_service_name_length information, short_service_name_byte_pair( ) element, provider_id information, service_status information, sp_indicator information, num_service_level_descriptor information, service_level_descriptor( ) element, num_FIT_level_descriptor information, and/or FIT_level_descriptor( ) element.

The FIT_protocol_version information may be information indicating a version of an FIT structure.

The Broadcast_stream_id information may be information for identifying an entire broadcast stream.

The FIT_section_number information may be information indicating a section number. The FIT may include a plurality of FIT sections.

The total_FIT_section_number information may be information indicating the number of all FIT sections of the FIT partially including the section. The information may be the same as FIT_section_number information with a highest value.

The FIT_section_version information may be information indicating a version number of an FIT section. A value of the information may be increased by 1 when information in the FIT section is changed. When a value of the information reaches a maximum value, a value of the information may return back to 0.

The FIT_section_length information may be information indicating a byte number of an FIT section including information items subsequent to the information.

The num_services information may be information indicating the number of services described by instance of the FIT. Services having at least one component may be included in each broadcast stream.

The service_id information may be information indicating a number for uniquely indicating a service in a range of a broadcast area.

A value of the SLS_data_version information may be increased at a time point when any one of signaling tables for a service transmitted via service layer signaling is changed or a time point when a service entry for services in an FIT is changed. The information may permit the receiver to observe the FIT and to recognize change in signaling for a service when the signaling for the service is changed.

The service_category information may be information for identifying a category of a service. When a value of the information is ‘0x00’, this indicates that a category of a service is not identified by the information, when the value is ‘0x01’, this indicates that a service corresponds to an audio/video (A/V) service, when the value is ‘0x02’, this indicates that a service corresponds to an audio service, when the value is ‘0x03’, this indicates that a service is an application-based service, and when the value is ‘0x01’ and the value is ‘0x08’, a service indicates that a service is service guide (service announcement). A value other than a value to which the information is allocated may be reserved for the future use.

The provider_id information may be information for identifying a provider for broadcasting a service.

The short_service_name_length information may be information indicating the number of bytes in the short_service_name_byte_pair( ) element. When a short name is not provided for a service, a value of the information may be 0.

The short_service_name_byte_pair( ) element may be information indicating a short name of a service. Each character may be encoded in the form of UTF-8. When an odd-numbered byte is present in the short name, a second byte of a last byte pair may include 0x00 every pair count identified by the short_service_name_length information.

The service_status information may be information indicating a state of a service (active/inactive and/or hidden/shown). An uppermost bit of the information may indicate whether the service is active (when a value is set to ‘1’) or inactive (when a value is set to ‘0’) and a lower most bit may indicate whether a service is hidden (when a value is set to ‘1’) or shown (when a value is set to ‘0’).

The sp_indicator information may be information for identifying whether one or more components required for meaningful expression are protected when the value is set. When a value of the information is set to ‘0’, the information may indicate that there is no component to be protected among components required for meaningful expression of a service.

The num_service_level_descriptor information may be information indicating the number of service level descriptors for a service.

The service_level_descriptor( ) element may include 0 or more service level descriptors for providing additional information for a service.

The num_FIT_level_descriptor information may be information indicating the number of FIT level descriptors for the FIT.

The FIT_level_descriptor( ) element may include 0 or more descriptors for providing additional information for the FIT.

FIG. 119 is a diagram illustrating a location of a descriptor to be included in signaling for a broadcast system according to an embodiment of the present invention.

0 or more descriptors for providing additional information for a service or a FIT may be included in a signaling structure.

The descriptor illustrated in the drawing may indicate a name and location of a descriptor to be included in a FIT level descriptor or a service level descriptor in the FIT.

The FIT may include broadcast_signaling_location_descriptor( ), inet_signaling_location_descriptor( ), and/or capability_descriptor( ).

The broadcast_signaling_location_descriptor( ) may be included in a region for signaling information about a location or a service included in the service level descriptor of the FIT.

The inet_signaling_location_descriptor( ) may be included in a location included in the service level descriptor or a location included in the FIT level descriptor.

The capability_descriptor( ) may be included in a region for signaling information of a location or a service included in the service level descriptor of the FIT.

FIG. 120 is a diagram illustrating broadcast_signaling_location_descriptor( ) according to an embodiment of the present invention.

The broadcast_signaling_location_descriptor( ) may include information for bootstrapping an address of a service layer signaling address for each service and a receiver may acquire an SLS transmitted through a broadcast network in a corresponding address.

The broadcast_signaling_location_descriptor( ) may include descriptor_tag information, descriptor_length information, IP_version_flag information, SLS_source_IP_address_flag information, SLS_source_IP_address information, SLS_destination_IP_address information, SLS_destination_UDP_port information, SLS_TSI information, and/or SLS_PLP_ID information.

The descriptor_tag information may be information for identifying a descriptor.

The descriptor_length information may be included in a descriptor and may be information indicating a size (length) of information subsequent to the information.

The IP_version_flag information may be information indicating a version of an IP used in an IP address transmitted in the present descriptor. When a value of the information is set to ‘0’, this indicates that the SLS_source_IP_address information and the SLS_destination_IP_address information are an IPv4 address and, when a value of the information is set to ‘1’, this indicates that the SLS_source_IP_address information and the SLS_destination_IP_address information are an IPv6 address.

The SLS_source_IP_address_flag information may be information for identifying whether the SLS_source_IP_address information is present.

The SLS_source_IP_address information may indicate a source IP address of packets for transmitting an SLS.

The SLS_destination_IP_address information may indicate a destination IP address of packets for transmitting an SLS.

The SLS_destination_UDP_port information may indicate a port number of a destination of packets for transmitting an SLS.

The SLS_TSI information may be information for identifying a delivery session for transmitting an SLS.

The SLS_PLP_id information may be information for identifying a location/region for transmitting an SLS. The SLS_PLP_id information may be information for identifying a PLP including an SLS. The SLS_PLP_id information may be transmitted in link layer signaling. In some cases, the information may be transmitted in signaling included in a link layer.

FIG. 121 is a diagram illustrating the meaning of inet_signaling_location_descriptor( ) and URL_type information according to an embodiment of the present invention.

The inet_signaling_location_descriptor( ) may include a URL indicating a location where a receiver is capable of receiving requested type of data from an external server through a broadband. The receiver may use one URL included in the descriptor as a query term for acquiring signaling description through a broadband.

The inet_signaling_location_descriptor( ) may include descriptor_tag information, descriptor_length information, provider_id information, URL_type information, and/or URL_bytes( ) information.

The descriptor_tag information may be information for identifying the descriptor.

The descriptor_length information may be information indicating that information is included in a descriptor and indicating a size (length) of subsequent information of the information.

The provider_id information may be information for identifying a provider for broadcasting a service.

The URL_type information may be information indicating a type of a URL expressed by the URL_bytes( ). When a value of the information is “0x00”, this indicates that an expressed URL is a URL of a signaling server for providing signaling and, when a value of the information is “0x01”, this indicates that an expressed URL is a URL of an ESG server for providing ESG data.

The URL_bytes( ) information may indicate a uniform resource location (URL) and each character included in the RUL may be encoded using a UTF-8 method. The URL may be used in a query term and the base URL may be extended by a query term to indicate a resource.

When resources are available through a broadband network, the inet_signaling_location_descriptor( ) may provide URL information for these resources.

FIG. 122 is a diagram illustrating a query term using URL_bytes information of inet_signaling_location_descriptor( ) according to an embodiment of the present invention.

The inet_signaling_location_descriptor( ) may be positioned at an FIT level and a URL may be used as a query term indicating a type of a resource requested by the URL. When the resource type corresponds to an SLS, a URL indicating where a receiver acquires a SLS through a broadband for all services described in the FIT may be included in the inet_signaling_location_descriptor( ). In this case, optionally, svc string may be used and attached to a last portion of the query term to permit the receiver to make a request for a SLS for a specific service. A response to the query term may b have an SLS fragment encapsulated in a multi part.

When a resource type is an ESG, a URL indicating where the receiver is capable of acquiring ESG through a broadband for all providers described in the FIT may be included in the inet_signaling_location_descriptor( ). In this case, optionally, prv string may be used and attached to a last portion of the query term to permit the receiver to make a request for the ESG for a specific provider.

The inet_signaling_location_descriptor( ) may be transmitted through a loop for a service level descriptor and, in this case, the inet_signaling_location_descriptor( ) may indicate a URL of a location for acquiring service layer signaling included in a service through a broadband. When the service_category information indicates that a category of a service is an A/V service, a URL may be used as a query term indicating desired signaling description. When a broadcaster provides another SLS URL for each service, the query term may be used and, in this case, a query term for adding svc string may not be used. A response to the query term may have SLS fragment encapsulated in a multi part.

An upper portion of the drawing illustrates an embodiment of a query term using the URL_bytes information when the inet_signaling_location_descriptor( ) is positioned at an FIT level and a lower portion of the drawing illustrates an embodiment of a query term using URL_bytes information when the inet_signaling_location_descriptor( ) is positioned at a service level.

A query term according to an embodiment of the present invention may be used as a query for making a request for entire SLS Set—SLS, a query for making a request for SLS Diff—Diff data of SLS, a query for making a request for SLS Template—SLS template, a query for making a request for USD—USD, a query for making a request for S-TSID—S-TSID, and/or a query for making a request for ESG—ESG.

FIG. 123 is a diagram illustrating capability_descriptor( ) according to an embodiment of the present invention.

The capability_descriptor( ) may provide a list of “capabilities” (e.g., download protocol, FEC algorithm, wrapper/archive format, compression algorithm, and media type) used for one service. A receiver may parse and process capability_descriptor( ) and, when required capabilities identified by information in the capability_descriptor( ) is not capable of being supported, requirements of a corresponding service may be avoided.

The capability_descriptor( ) may include descriptor_tag information, descriptor_length information, and/or capabilities_bytes( ) element.

The descriptor_tag information may be information for identifying the descriptor.

The descriptor_length information may be included in the descriptor and may be information indicating a size (length) of subsequent information of the information.

The capabilities_bytes( ) element may indicate information on string type of capabilities. The capabilities_bytes( ) element may include information included in the aforementioned capability_descriptor.

FIG. 124 is a diagram illustrating FIT defined in XML according to an embodiment of the present invention.

The FIT defined in the XML may include @bsid information, @fitSectionNumber information, @totalFitSectionNumber information, @fitSectionVersion information, Service element, @serviceId information, @providerId information, @serviceCategory information, @spIndicator information, @serviceStatus information, @shortServiceName information, @SLSVersion information, capabilityCode element, inetSignalingLocation element, @urlType information, @url information, broadcastSignalingLocation element, @IPVersion information, @sourceIPAddress information, @destinationIPAddress information, @destinationUdpPort information, @TSI information, @PLPID information, inetSignalingLocation element, @providerId information, @urlType information, and/or @url information.

The @bsid information may be information for identifying a broadcast stream.

The @fitSectionNumber information may be information indicating a number of the section. The FIT may include a plurality of FIT sections.

The @totalFitSectionNumber information may be information indicating the number of all FIT sections of an FIT including the section as a part. The information may be the same as FIT_section_number information with a highest value.

The @fitSectionVersion information may be information indicating a version number of an FIT section. A value of the information may be increased by 1 when information transmitted in the FIT section is changed. When a value of the information is reached to a maximum value, a value of the information may return back to 0.

The Service element may be an ATSC3.0 service entry. The Service element may include information related to the ATSC3.0 service.

The @serviceId information may be information uniquely indicating a service in a range of a broadcast area.

The @providerId information may be information for identifying a provider for broadcasting a service.

The @serviceCategory information may be information for identifying a category of a service. When a value of the information is ‘0x00’, this indicates that a category of a service is not identified by the information, when the value is ‘0x01’, this indicates that a service corresponds to an audio/video (A/V) service, when the value is ‘0x02’, this indicates that a service corresponds to an audio service, when the value is ‘0x03’, this indicates that a service is an application-based service, and when the value is ‘0x01’ and the value is ‘0x08’, this indicates that a service is service guide (service announcement). A value other than a value allocated to the information may be reserved for future use.

The @spIndicator information may be information indicating whether one or more components required for meaningful expression are protected when a value thereof is set. When a value of the information is set to ‘0’, the information may indicate that there is no component to be protected among components required for meaningful expression of a service.

The @serviceStatus information may be information indicating a state of a service (active/inactive and/or hidden/shown). The information may indicate whether a service is active (when a value is set to ‘1’), inactive (when a value is set to ‘0’), hidden (when a value is set to ‘3’), or shown (when a value is set to ‘2’).

The @shortServiceName information may be information indicating a short name of a service.

A value of the @SLSVersion information may be increased at a time point when any one of signaling tables for a service transmitted via service layer signaling is changed or a time point when a service entry for services in an FIT is changed. The information may permit the receiver to observe the FIT and to recognize change in signaling for a service when the signaling for the service is changed.

The capabilityCode element may include information indicating capability group and capability required by the receiver to generate meaningful expression of content of the ATSC3.0 service. The present element may include entire and partial information of information to be included in the aforementioned capability_descriptor.

The inetSignalingLocation element may include a URL indicating a location where the receiver is capable of receiving requested type of data from an external server through a broadband. The inetSignalingLocation element may include entire or partial information included in the aforementioned inet_signaling_location_descriptor( ).

The @urlType information may be information indicating a type of a URL. When a value of the information is “0x00”, this indicates that an expressed URL is a URL of a signaling server for providing signaling and, when a value of the information is “0x01”, this indicates that the expressed URL is a URL of an ESG server for providing ESG data.

The @url information may information indicating a URL of a location where service layer signaling that belongs to a service is acquired. When a category of a service is not an ESG service, the URL may be used as a query term indicating a desired signaling fragment. When a broadcaster provides another SLS URL for each service, a corresponding URL may be used and svc string may not be used in a query term. A base URL may be extended by one or more queries to indicate desired resources and an embodiment thereof has been described above. When a category of the service is an ESG service, the URL may indicate an Internet server in which the ESG is to be acquired.

The broadcastSignalingLocation element may include information for bootstrapping an address of a service layer signaling for each service and the receiver may acquire an SLS transmitted through a broadcast network at a corresponding address.

The @IPVersion information may be information indicating a version of an IP used in an IP address. According to setting of a value of the information, this indicates whether the SLS_source_IP_address information and the SLS_destination IP address information is an IPv4 address or an IPv6 address.

The @sourceIPAddress information may indicate a source IP address of packets for transmitting an SLS.

The @destinationIPAddress information may indicate a destination IP address of packets for transmitting an SLS.

The @destinationUdpPort information may indicate a port number of a destination of packets for transmitting an SLS.

The @TSI information may be information for identifying a delivery session for transmitting an SLS.

The @PLPID information may be information for identifying a position/region in which an SLS is transmitted. The @PLPID information may be information for identifying a PLP including an SLS. The @PLPID information may be transmitted in link layer signaling. The information may be transmitted in signaling transmitted in a link layer in some cases.

The inetSignalingLocation element may include a URL indicating a location where the receiver is capable of receiving a requested type of data from an external server through a broadband. The inetSignalingLocation element may include entire or partial information included in the aforementioned inet_signaling_location_descriptor( ).

The @providerId information may be information for identifying a provider for broadcasting the service.

The @urlType information may be information indicating a type of a URL. When a value of the information is “0x00”, this indicates that an expressed URL is a URL of a signaling server for providing signaling and, when a value of the information is “0x01”, this indicates that an expressed URL is a URL of an ESG server for providing ESG data.

The @url information may be information indicating a URL of a location where service layer signaling that belongs to a service is capable of being acquired. A description of the @url information may be the same as a description of the URL_bytes information of the inet_signaling_location_descriptor( ).

According to an embodiment of the present invention, the LLS may include emergency alert description (EAD) or rating region description (RRD).

The EAD may be referred to as an emergency alert table (EAT) and may include information for emergency alert.

The RRD may be referred to as a rating region table (RRT) and may include information related to watching restriction.

FIG. 125 is a diagram illustrating a data model of service layer signaling for a linear service according to an embodiment of the present invention.

The service layer signaling (SLS) may provide technological information required for a receiver to discover and access an ATSC3.0 user service and content components thereof. The service layer signaling may include a set of metadata fragments coded in the form of XML transmitted through a dedicated LCT session. The LCT session for transmitting the SLS may be acquired using bootstrapping information included in the FIT as described above. The SLS may be defined for each service level and may describe access information and attribute of a service, such as a list of content components of a service and how the components are acquired. The SLS may include information on receiver capabilities required to generate meaningful expression of a service. In a ROUTE/DASH system, the SLS may include USBD, S-TSID, and/or MPD to transmit a linear service. The SLS fragments may be transmitted through a dedicated LCT delivery session having a pre-known TSI value.

Referring to the drawing, the USBD may include a USD and the USD may include fullMPDUri information that is information for acquiring MPD. The receiver may acquire the MPD by using fullMPDUri information. The USD may include information for connecting a specific service and a related S-TSID and the receiver may acquire information of the corresponding S-TSID to express a specific service by using the information.

FIG. 126 is a diagram illustrating user service bundle description (USBD) according to an embodiment of the present invention.

The USBD may be an entry point of SLS fragment or uppermost level fragment. The USBD may comply with basic content of a USD defined in the 3GPP MBMS and include the following extension for the ATSC3.0 service.

The USBD may be a child element and may include atsc:serviced information, atsc:fullMPDUri information, atsc:sTSIDUri information, and atsc:capabilityCode information below userServiceDescription element.

The USBD may be a child element and may include atsc:broadcastAppService information, broadcast stream ID as child attribute thereof, and/or basePattern element below deliveryMethod element.

The USBD may be a child element and may include atsc:unicastcastAppService and information and/or basePattern element as a child element thereof below deliveryMethod element.

The USBD may include bundleDescription root element. The bundleDescription root element may have userServiceDescription element. The userServiceDescription element may be instance of one service.

The userServiceDescription element may include @serviceId, @atsc:serviceId, @atsc:fullMPDUri, @atsc:sTSIDUri, name, serviceLanguage, atsc:capabilityCode, and/or deliveryMethod.

The @serviceId may be a globally unique service identifier.

The @atsc:serviced may be a reference for a service entry corresponding to LLS (FIT or SLT). A value of corresponding attribute may be the same as a value of serviced allocated to a corresponding entry defined in the LLS.

The @atsc:fullMPDUri may be information for referencing (or connecting) MPD fragment including description of a content component of a service transmitted in a broadband or optionally in broadcast.

The @atsc:sTSIDUri may be information for referencing (or connecting) S-TSID fragment for providing an access related parameter in a delivery session for transmitting content of a corresponding service.

The name may indicate a name of a service given according to lang attribute. The name element may include lang attribute indicating a language of a service name. The language may be specified according to an XML data type.

The serviceLanguage may indicate an available language of a service. The language may be specified according to an XML data type.

The atsc:capabilityCode may specify capabilities required for a receiver to generate meaningful presentation of a corresponding service. In some embodiments, the present field may specify a pre-defined capability group. Here, the capability group may be a group capability attribute value for meaningful presentation. The present field may be omitted in some embodiments.

The deliveryMethod may be a container of transport related to information that belongs to content of a service in broadcast and (optionally) broadband modes of access. With regard to data included in a corresponding service, when the number of data is N, delivery methods of each data may be described by the element. The deliveryMethod element may include atsc:broadcastAppService element and atsc:unicastAppService element. Each lower element may have basePattern element as a lower element.

The atsc:broadcastAppService may be DASH representation transmitted in multiplexed or non-multiplexed form of broadcast including a corresponding media component that belongs to a service over all periods of the belonging media presentation. That is, each of the present fields may refer to DASH representations transmitted through a broadcast network.

The atsc:unicastAppService may be DASH representation transmitted in multiplexed or non-multiplexed form of broadband including configuration media content component that belongs to a service over all periods of belonging media presentation. That is, each of the present fields may refer to DASH representations transmitted through a broadband.

The basePattern may be a character base used by a receiver to be matched with all portions of segmentation URL used by a DASH client in order to make a request for media segmentation of parent representation in an included period. The matching may suggests delivery of the corresponding requested media segmentation in broadcast transport. With regard to a URL address for receiving DASH representation expressed in atsc:broadcastAppService element and atsc:unicastAppService element, a portion of the URL may have a specific pattern and the pattern may be described by the present field. A predetermined portion of data may be separated through the information. In some embodiments, proposed default values may be changed. The illustrate use columns may be related to each field and, in this case, M may refer to a mandatory field, O may refer to an optional field, OD may refer to an optional field with a default value, and CM may refer to a conditionally mandatory field. 0 . . . 1 to 0 . . . N may refer to the number of available corresponding fields.

FIG. 127 is a diagram illustrating an S-TSID according to an embodiment of the present invention.

The S-TSID may be SLS XML fragment for providing entire session description information on a delivery session for transmitting a content component of a service. The S-TSID may be SLS metadata segmentation including entire delivery session descript information of a configuration LCT session for transmitting a media content component of a service and 0 or more ROUTE sessions. The S-TSID may include file metadata of a delivery object or object flow transmitted in an LCT session of a service as well as content component transmitted in an LCT session and additional information on payload format.

Each case of S-TSID fragments may be referenced in USBD fragment by @atsc:sTSIDUri attribute of userServiceDescription element. The S-TSID may be expressed in binary format or XML document form.

The illustrated S-TSID may have an S-TSID root element. The S-TSID root element may include @serviceId, RS, and/or MS.

The @serviceID may be a reference corresponding to a service element in LLS (FIT). A value of the corresponding attribute may reference a service having a corresponding value of service_id in the FIT. The information may not use a ROUTE session and may be present when an MMTP session for broadcast transmission for a linear service that does not use USD is used.

The RS element may have information on a ROUTE session for transmitting corresponding service data. Service data and service components are transmitted through a plurality of ROUTE sessions and, thus, the present element may have the number of 1 to N.

The RS element may include @bsid, @sIpAddr, @dIpAddr, @dport, @PLPID, and/or LS.

The @bsid may be an identifier of a broadcast stream in which a content component of broadcastAppService is transmitted. When corresponding attribute is not present, a PLP of a default broadcast stream may transmit SLS fragment of a corresponding service. The value may be the same value as broadcast_stream_id in FIT (SLT).

The @sIpAddr may indicate a source IP address. Here, the source IP address may be a source IP address of a ROUTE session for transmitting a service component included in a corresponding service. As described above, service components of one service may be transmitted through a plurality of ROUTE sessions. Accordingly, the service component may be transmitted through other ROUTE session but not a ROUTE session for transmitting the corresponding S-TSID. Accordingly, to indicate a source IP address of the ROUTE session, the present field may be used. A default value of the present field may be a source IP address of a current ROUTE session. When a service component transmitted through other ROUTE sessions is present and needs to indicate the ROUTE session, a value of the present field may be a source IP address value of the ROUTE session. In this case, the present field may be M, i.e., a mandatory field.

The @dIpAddr may indicate a destination IP address. Here, the destination IP address may be a destination IP address of a ROUTE session for transmitting a service component included in a corresponding service. For a case such as a description of the @sIpAddr, the present field may indicate a destination IP address of a ROUTE session for transmitting a service component. A default value of the present field may be a destination IP address of a current ROUTE session. When a service component transmitted through other ROUTE sessions is present and needs to indicate the ROUTE session, a value of the present field may be a destination IP address value of the ROUTE session. In this case, the present field may be M, i.e., a mandatory field.

The @dport may indicate a destination port. Here, the destination port may be a destination portion of a ROUTE session for transmitting a service component included in a corresponding service. For a case such as a description of the @sIpAddr, the present field may indicate a destination port of a ROUTE session for transmitting a service component. A default value of the present field may be a destination port number of a current ROUTE session. When a service component transmitted through other ROUTE sessions is present and needs to indicate the ROUTE session, a value of the present field may be a destination port number value of the ROUTE session. In this case, the present field may be M, i.e., a mandatory field.

The @PLPID may be an ID of a PLP for a ROUTE session represented by RS. A default value may be an ID of a PLP of an LCT session including a current S-TSID. In some embodiments, the present field may have an ID value of a PLP for an LCT session for transmitting an S-TSID in a corresponding ROUTE session and have ID values of all PLPs for a corresponding ROUTE session. Information such as @PLPID may be included in signaling transmitted through a link layer and transmitted to a receiver.

The LS element may have information on an LCT session for transmitting corresponding service data. Service data and service components are transmitted through a plurality of LCT sessions and, thus, the present element may have the number of 1 to N.

The LS element may include @tsi, @PLPID, @bw, @startTime, @endTime, SrcFlow, and/or RprFlow.

The @tsi may indicate a TSI value of an LCT session for transmitting a service component of a corresponding service.

The @PLPID may have ID information of a PLP for a corresponding LCT session. The value may cover a basic ROUTE session value.

The @bw may indicate a maximum bandwidth value. The @startTime may indicate a start time of a corresponding LCT session. The @endTime may indicate an end time of a corresponding LCT session. The SrcFlow element may describe a source flow of ROUTE. The RprFlow element may describe repair flow of ROUTE.

Proposed default values may be changed in some embodiments. The illustrated use columns may be related to each field and, in this case, M may refer to a mandatory field, O may refer to an optional field, OD may refer to an optional field with a default value, and CM may refer to a conditionally mandatory field. 0 . . . 1 to 0 . . . N may refer to the number of available corresponding fields.

The MS element may include @versionNumber information, @bsid information, @sIpAddr information, @dIpAddr information, @dport information, @packetId information, @PLPID information, @bw information, @startTime information, and/or @endTime information.

The MS element may be an element including information for an MMTP session. The information included in the MS element may be transmitted in an MMT signaling message.

The @versionNumber information may be information indicating a version number of an MMTP protocol used in an MMTP session.

The @bsid information may be information indicating an identifier of a broadcast stream in which content components are transmitted.

The @sIpAddr information may be information indicating a source IP address of a packet for transmitting a content component.

The @dIpAddr information may be information indicating a destination IP address of a packet for transmitting a content component.

The @dport information may be information indicating a destination port number of a packet for transmitting a content component.

The @packetId information may be information indicating MMTP packet_id for transmitting an MMT signaling message of the MMTP session.

The @PLPID information may be information for identifying a PLP for an MMTP session. The @PLPID information may be included in signaling transmitted through a link layer.

The @bw information may be information indicating a maximum bandwidth allocated for an MMTP session.

The @startTime information may be information indicating a start time of an MMTP session.

The @endTime information may be information indicating an end time of an MMTP session.

Hereinafter, media presentation description (MPD) for ROUTE/DASH will be described.

The MPD may be SLS metadata fragment including formulated description of the DASH media presentation corresponding to a linear service of given duration determined by a broadcaster (e.g., one TV program for a period or a set of consecutive linear TV programs). Content of MPD may provide content of a resource identified in media presentation and a source identifier of fragment. A data structure and semantics of MDP segmentation may comply with MPD defined by the MPEG DASH.

One or more DASH representations transmitted in the MPD may be transmitted in broadcast. The MPD may describe additional representation transmitted in broadband like in a hybrid service or support service continuity to broadcast from broadcast due to broadcast signal degradation (e.g., driving in a tunnel).

FIG. 128 is a diagram illustrating ATSC_physical_layer_pipe_identifier_descriptor( ) according to an embodiment of the present invention.

When MMTP sessions are used to transmit an ATSC3.0 streaming service, an MMT signaling message may be transmitted by an MMTP according to a signaling message mode defined in the ISO/IEC 23008-1. Each MMTP session may transmit components with an MMT signaling message and packets for transmitting the MMT signaling message may be signaled by an MS element in S-TSID fragment.

As defined in the ISO/IEC 23008-1, the MMT signaling message may include PA, MPI, MPT, and HRBM messages and an MP table in the MMT signaling message may transmit asset location information for ATSC3.0 service components. In this case, the illustrated ATSC_physical_layer_pipe_identifier_descriptor( ) may be transmitted as asset_descriptor( ) of the MP table. When the ATSC_physical_layer_pipe_identifier_descriptor( ) is not present, asset may be transmitted through the same PLP as a PLP indicated by MS@PLPID information in the S-TSID fragment.

The ATSC_physical_layer_pipe_identifier_descriptor( ) may include descriptor_tag information, descriptor_length information, and/or PLP_id information.

The descriptor_tag information may be information for identifying the descriptor.

The descriptor_length information may be included in the descriptor and may be information indicating a size (length) of subsequent information of the information.

The PLP_id information may be information of an identifier of a PLP including MMTP packets for asset described by the descriptor.

FIG. 129 is a diagram illustrating a layered signaling structure of an ATSC3.0 system according to an embodiment of the present invention.

The drawing illustrates the case in which two S-TSID instances are transmitted through ROUTE. A first S-TSID may provide access information for LCT sessions included in ROUTE session #1. The ROUTE session #1 may transmit content components of service_X. A second S-TSID may provide access information for LCT sessions included in ROUTE session #N and the ROUTE session #N may transmit content components of service_Y.

A receiver may acquire LCT sessions for transmitting components for each service by using information included in the aforementioned S-TSID fragment.

Prior to the aforementioned acquisition procedure of a component of a service, the receiver may perform a procedure of scanning services.

FIG. 130 is a diagram illustrating a flow of a rapid channel scan procedure according to an embodiment of the present invention.

According to an order shown in the numbers illustrated in the drawing, the rapid channel scan procedure may be performed.

First, a tuner in the receiver may scan frequencies by using a pre-defined frequency list.

Second, the tuner may be on standby to receive a signal for each frequency.

Third, when a signal is detected from one frequency, a baseband processor may extract an FIT and transmit the FIT to a middleware module.

Fourth, the middleware module may transmit the FIT to an FIT parser.

Fifth, the FIT parser may parse data of the FIT to extract information. Even if FITs with the same version number are present in the receiver in a last scan procedure, a re-parsing procedure may be a most appropriate processing procedure in terms of stability. This is because there is possibility that increase in version number returns back to a first version number over a maximum value and an FIT with the same version number as a previous case is accidently transmitted. In a scenario in which the FIT is not updated, the receiver may perform a procedure of initializing a version number of the FIT.

Sixth, information extracted from the FIT may be stored in a channel map (a database or a storage).

FIG. 131 is a diagram illustrating a flow of an entire channel scan procedure according to an embodiment of the present invention.

When a receiver performs entire scan on service signaling (USBD or USD) for each service, the receiver may store or acquire more abundant information. For example, a relatively long service name may be acquired from the USD and the USD and a service_id value in the FIT may be matched and stored as a corresponding service in a channel map.

A procedure of entire scan of a service may be performed on a service in an order of the number illustrated in the drawing.

First, a tuner in a receiver may scan frequencies by using a predefined frequency list.

Second, the tuner may be on standby to receive a signal for each frequency.

Third, when a signal is detected from one frequency, a baseband processor may extract an FIT and transmit the FIT to a middleware module.

Fourth, the receiver may check whether FIT_version is new or not. Even if FITs with the same version number are present in the receiver in a last scan procedure, a re-parsing procedure of the receiver may be a most appropriate processing procedure in terms of stability. This is because there is possibility that increase in version number returns back to a first version number over a maximum value and an FIT with the same version number as a previous case is accidently transmitted. In the case of a new version, the middleware module may collect the FIT and transmit the FIT to an FIT parser.

Fifth, The FIT parser may parse data of the FIT to extract information. Even if FITs with the same version number are present in the receiver in a last scan procedure, a re-parsing procedure may be a most appropriate processing procedure in terms of stability.

Sixth, information extracted from the FIT may be stored in a channel map (a database or a storage).

Seventh, the receiver may obtain SLS bootstrapping information from the FIT.

Eighth, the receiver may transmit the SLS bootstrapping information to a ROUTE client.

Ninth, the receiver may perform signaling filter and acquire and store the USD to extract the USD from the SLS.

Tenth, a signaling parser may parse the USD. Here, even if SLSs with the same version number are present in the receiver in a last scan procedure, a re-parsing procedure of the receiver may be a most appropriate processing procedure in terms of stability. This is because there is possibility that increase in version number returns back to a first version number over a maximum value and an SLS with the same version number as a previous case is accidently transmitted.

Eleventh, the receiver may be mapped to service_id and update a channel map.

FIG. 132 is a diagram illustrating a procedure of acquiring a service in pure broadcast according to an embodiment of the present invention.

When video and audio segments are transmitted via pure broadcast with one ROUTE session, service acquisition using service signaling may be performed in the following order.

First, USD, S-TSID, and MPD may be acquired and parsed together. All tables are required for service acquisition.

Then, representation for expression may be selected. In this case, an S-TSID needs to be checked to determine representation transmitted through a broadcast network.

Then, a receiver may transmit information to a segment acquisition module for providing user preference by using corresponding signaling from signaling (USD, S-TSID, and MPD). For example, the user may prefer Spanish audio to English audio. In this case, information associated with user preference may be stored in the receiver and a component of a service provided in Spanish preferred by a user may be selected using the information and information related to audio in USD, S-TSID, and/or MPD.

Then, the segment acquisition module may determine whether a component transmitted through a broadcast stream is capable of being acquired, using information described in the USD. The segment acquisition module may recognize where a component is capable of being acquired, using the USD. When a DASH client makes a request for one segment from an internal proxy server, the internal proxy server needs to recognize whether to make a request for a corresponding segment from a remote broadband server (when a corresponding segment is not present) or to be on standby until a corresponding segment appears in a broadcast stream. The USD may describe multicast “base patterns” and unicast “base patterns” in deliveryMethod element. The proxy server may check whether unicast base patterns or multicast base patterns are substring of a URL submitted by a DASH player and operate according to the result.

Then, in the case of pure broadcast, the receiver may recognize where components are capable of being acquired even if deliveryMethod element is not present in the USD.

FIG. 133 is a diagram illustrating a procedure of acquiring a service a plurality of ROUTE sessions in pure broadcast according to an embodiment of the present invention.

The plurality of ROUTE sessions may be used to transmit data or components included in one service. In this case, an S-TSID may include additional ROUTE session information required to access all representations.

Referring to the drawing, a receiver may receive an FIT and acquire an SLS for a specific service. The receiver may acquire an S-TSID for providing information on a ROUTE session/LCT session allocated to a corresponding service with reference to information on a USD in the acquired SLS. The S-TSID may indicate that transmission of components of service #1 is performed by ROUTE session #1 and ROUTE session #2. To receive components of service #1, the receiver may refer to information on ROUTE session #2 as well as information on ROUTE session #1 to be included in the S-TSID.

FIG. 134 is a diagram illustrating a procedure of bootstrapping electronic service guide (ESG) via a broadband network, according to an embodiment of the present invention.

The bootstrapping of the ESG via a broadband network may be signaled in an FIT. Referring to the drawing, all ESG data may be transmitted via a broadband. Accordingly, ESG broadcast bootstrapping information in the FIT may be replaced with ESG broadband bootstrapping information. For example, URL_type of inet_signaling_location_descriptor( ) may indicate whether a type of a URL is an ESG or not.

Referring to the drawing, the receiver may first acquire the FIT and parse inet_signaling_location_descriptor( ) in the FIT. As described above, the inet_signaling_location_descriptor( ) may provide a URL of a service for providing the ESG and the receiver may access the URL to acquire ESG data through a broadband.

FIG. 135 is a diagram illustrating a procedure of acquiring a service through broadcast and broadband according to an embodiment of the present invention.

When two or more audio components with different languages are transmitted through different paths, one component may be transmitted through a broadcast network and the other component may be transmitted through a broadband network. In this case, the S-TSID may include information for describing all broadcast components such that a ROUTE client acquires desired components. When a DASH client makes a request for segment, the USD may include URL patterns for a broadcast network and URL patterns for a broadband network to describe a transmission path and segments by a transmission target of a receiver middleware. In this case, the middleware may recognize a segment requested from remote broadband server by the middleware and segment to be searched from in a broadcast network.

Referring to the drawing, the receiver may acquire an FIT from a broadcast signal and receive an SLS of a specific service by using information in the FIT. The receiver may recognize that each component is transmitted through a broadcast network and a broadband network for a corresponding service by using information in the USD (or USBD) in the SLS. For example, an English audio component for a corresponding service may be transmitted through a broadcast network and a Spanish audio component may be transmitted through a broadband network. The USD may include base pattern information used to acquire an English audio component transmitted through a broadcast and include base pattern information used to acquire a Spanish audio component transmitted through a broadband network. The English audio component may be acquired using information in the USD and information in the S-TSID and the Spanish audio component may be received from an external server by using the information in the USD. The receiver may perform a switching operation between the English audio component and the Spanish audio component by using the information of the MPD.

FIG. 136 is a diagram illustrating signaling for an operation of changing service reception between broadcast and broadband according to an embodiment of the present invention.

A receiver may change reception to a broadband network from a broadband network or to a broadband network from a broadband network. The receiver may use signaling information included in the USD during this procedure. The USD may include information on whether components are transmitted through a broadcast network or a broadband network. A receiver middleware may receive a component through a broadcast network if possible or may acquire a component through a broadband network when there is a problem in terms of reception through a broadcast network.

Referring to the drawing, the receiver may acquire the FIT and the SLS and parse a USD in the SLS. The USD may indicate that a video component and an audio component included in a service are transmitted through a broadcast network and a broadband network and include base pattern information required to receive a component in each of a broadcast network and a broadband network. The receiver may acquire a component through one path according to quality of a broadcast network or broadband network connected to the receiver by using information in the USD. Change between components transmitted through a broadcast network and a broadband network may be performed by the receiver by using the information in the MPD.

FIG. 137 is a diagram illustrating signaling of receiver capability information according to an embodiment of the present invention.

As described above, all or some of fragment of the SLS may include information indicating receiver capability required to meaningfully express a specific service or components.

According to an embodiment of the present invention, a scalable coding method may be applied to a service or a component and a receiver may process data to which scalable coding is applied.

First, according to an embodiment of the present invention, the USD may include information on capability required to render a service. For example, to decode video, video resolution is necessary capability. To this end, the USD may have a capability value of “HD” or “UHD”. This may indicate that a current service or program is provided in HD or UHD. The USD may also include capability for processing other component such as audio, closed caption, or an available application.

Then, the receiver may recognize a component that is provided to render a UHD service or a HD service by using information in the MPD. That is, referring to the drawing, @dependencyId in the MPD may include information for identifying representation dependent upon representation of video. The receiver may provide HD video by using basic video representation (Rv) and provide UHD video by further using enhanced video representation (Rev).

FIG. 138 is a diagram illustrating the meaning of an LCT transport object identifier (TOI) for filtering signaling fragment and information included in the field according to an embodiment of the present invention.

To rapidly filter signaling fragment as a target by a receiver, the LCT TOI field may be divided into three parts.

A first part may be a fragment type part and may be allocated into the TOI field to identify a type of the signaling fragment.

A second part may be a fragment type extension part and may be allocated into the TOI field to identify a sub type of fragment. In an embodiment of allocating a sub type, when a plurality of fragments are transmitted, a type of fragment of bit map format included in an object may be identified to filter separate fragment. In another embodiment of allocating a sub type, when a plurality of instances of signaling fragments with the same fragment types are transmitted (e.g., when a plurality of MPDs are present at a program boundary), this indicates an identifier of instance.

A third part may be a version part and may be allocated into the TOI field to indicate an object identified by a fragment type extension part and a fragment type part.

The LCT TOI field according to the present embodiment may be divided into a fragment type part, a fragment type extension part, and/or a version part.

The fragment type part may include a value for identifying a type of service layer signaling transmitted by a current object. For example, when a value of the fragment type part is ‘0x00’, this indicates that a bundle of SLSs is transmitted through the object, when a value of the fragment type part is ‘0x01’, this indicates that USBD/USD of an SLS is transmitted through the object, when a value of the fragment type part is ‘0x02’, this indicates that a S-TSID of an SLS is transmitted through the object, and when a value of the fragment type part is ‘0x03’, this indicates that MPD of the SLS is transmitted through the object.

When an object includes a plurality of fragments, the fragment type extension part may be a bit map indicating fragment included in the object. When one fragment is included in the object, values for identifying a sub type of service signaling fragment for more detailed filtering may be allocated to the part. Referring to the drawing, when the fragment type part indicates that a bundle of SLSs is transmitted through one object, the fragment type part may identify whether a specific fragment corresponds to USBD/USD, S-TSID, or MPD according to a value of a fragment type extension type. When the fragment type part identifies signaling fragment included in one object (when a value of the fragment type part is ‘0x01’ to ‘0x03’), the fragment type extension part may have 16-bit of hashed value extracted from a URL of service layer signaling fragment and the part may be used to filter fragment having instance URL before a client assembles an LCT packet.

The version part may indicate a version number of all objects. When an object includes one fragment, the part may include a version number of corresponding fragment. When an object includes a set of fragments, the part may include a version number for an object and, accordingly, the case in which fragment included in the object may be identified. The version number of the object may be increased by 1b whenever fragment in the object is changed.

The case in which a value of TOI is 0 or 1 may be reserved for transmission of EFDT and, in this case, information of the TOI field may not be used to filter the EFDT. An LCT codepoint may be identified for a payload type and the receiver may use the field instead of a TOI value to determine a type of a payload transmitted through an LCT session.

FIG. 139 is a diagram illustrating MetadataEnvelope in the form of XML for application of template-based compression to signaling according to an embodiment of the present invention.

XML signaling fragments described in the present invention may be compressed using a compression tool such as Gzip but may be compressed with Diff and Patch tools by using other methods. During the Diff and Patch procedure, XML signaling template between a sender and a receiver may be pre-shared. This procedure may include comparing two XML files, XML signaling template and XML signaling instance to generate output indicating a difference between the two values referred to as Diff by a sender side.

Here, the signaling template may be use as a term indicating a basic structure of signaling fragment.

Here, the signaling instance may correspond to the aforementioned signaling fragment and may be used as a term indicating signaling fragment including information for a featuring service, content, and so on. For example, when the S-TSID is signaling fragment defined for one service, S-TSID fragment transmitted for the featuring service may be referred to as S-TSID instance.

The Diff may be encapsulated by a metadata envelope element, such as general XML signaling instance. When Diff is generated by a sender side, Diff may be encapsulated in content in an update element and, then encapsulated in metadata envelope. The metadata envelope may be transmitted to a plurality of receivers through a signaling channel. The receiver may receive and check the metadata envelope to check whether the metadata envelope element includes diffUpdate element. When the diffUpdate element is included in the metadata envelope element, the receiver may recognize that the diffUpdate element needs to be processed in the compression mode.

The receiver may search for signaling template of metadataURI attribute (SignalingTemplateID) with version attribute (SignalingTemplateVersion) in signaling templates that are pre-shared and stored. When the corresponding signaling template is not capable of being discovered, the receiver may attempt to acquire signaling template with URL of SignalingTemplateID via a GET procedure.

The receiver may apply the Diff transmitted to the acquired signaling template to recover signaling instance. The signaling fragment may have a pair of version attribute (SignalingInstanceVersion) and metadataURI attribute (SignalingInstanceID). It may be necessary to transmit only a difference (e.g., an element, an added attribute value, or changed or deleted content) as an updated portion of template instead of transmission of a complete file. The receiver may apply the difference to the signaling template to acquire signaling fragments (patch procedure). When it is necessary to transmit fragment with a very small difference via comparison with original complete fragment, if compress is performed via the Diff and Patch procedure, very high efficiency may be obtained in transmission and processing of data compared with a conventional compression method.

As described in the 3GPP-MBMS, metadata envelope and metadata fragment may be compressed using Gzip. Even if there is no update content in a server side, a diff message with no Diff may be transmitted to a client such that the client generates signaling fragment at a location in which instantiation of signaling fragment is required. The diff message with no Diff may be periodically transmitted and, accordingly, the receiver may periodically check signaling fragments.

The Diff may be defined in the form of XML and may include information of the aforementioned signaling fragment and/or content of a changed part of the element. The metadata envelope including the Diff may include information for identifying signaling fragment to which corresponding Diff needs to be applied and/or information indicating a version of signaling fragment to which corresponding Diff is applied. The receiver may check signaling fragment to which the Diff is applied by using information for identifying signaling fragment in the metadata envelope and check whether the Diff needs to be applied by using information indicating a version of signaling fragment to which Diff is applied. In the case of a different version, the receiver may apply content of Diff to the corresponding signaling fragment to update the corresponding signaling fragment and store the updated fragment.

FIG. 140 is a diagram illustrating a compression procedure of template-based signaling fragment according to an embodiment of the present invention.

The signaling template fragment may be identified by a URL included in content of templateID element. The template itself may be fetched and pre-shared through HTTP(s) via a broadband. Upon first obtaining a diff message, the receiver may store the diff message for the future use. The template corresponds to fragment instance at a specific time point and signaling fragment may be generated using a method applied to generate instance followed by a subsequent diff message. In this case, information for identifying a mode used by a fixed template or a mode in which a template is provided as fragment instance may be included in signaling.

Referring to the drawing, a sender side may generate signaling and generate signaling instance (aforementioned signaling fragment). The sender may compare the generated signaling instance and pre-transmitted (or pre-stored) signaling instance to generate a diff message including Diff. During a procedure of generating the diff message, the signaling template may be used. The sender may transmit the generated diff message to a receiver side.

The receiver side may receive the diff message and apply Diff included in the corresponding diff message to the signaling template to complete signaling instance. As described above, the signaling template may be pre-shared or signaling fragment that is first received by a receiver may be used as a template according to a mode. The receiver side may acquire the aforementioned signaling fragments in the present invention by using the completed signaling instance. The receiver side may acquire a service by using the acquired signaling fragment, as described above.

FIG. 141 is a flowchart illustrating a method of transmitting and processing a broadcast signal according to an embodiment of the present invention.

According to an embodiment of the present invention, a transmitter may generate broadcast data for one or more broadcast services (JS141010).

The transmitter may generate first level signaling information including information for describing attribute of one or more broadcast services (JS141020).

The transmitter may generate second level signaling information including information for listing one or more broadcast services (JS141030).

The transmitter may generate link layer packets including encoded broadcast data, the first level signaling information, and the second level signaling information (JS141030).

The transmitter may generate a broadcast signal including the generated link layer packets (JS141040).

A procedure of generating the first level signaling information by the transmitter may include generating signaling instance included in the first level signaling information, generating signaling template for the first level signaling information, generating Diff data including data about a difference between the generated signaling instance and the generated signaling template, and generating the first level signaling information including the Diff data.

According to an embodiment of the present invention, the Diff data may include signaling template identifier information for identifying signaling template to which the Diff data needs to be applied, and signaling template version information indicating a version of a signaling template identified by the signaling template identifier.

According to an embodiment of the present invention, the transmitter may transmit the generated signaling template to a receiver before transmitting the Diff data to the receiver.

According to an embodiment of the present invention, the transmitter may process the first level signaling information according to an asynchronous layered coding/layered coding transport (ALC/LCT) protocol to generate first level signaling LCT packets including the first level signaling information and to generate link layer packets including the generated LCT packets and the LCT packets may include a transmission object identifier (TOI) field for identifying an object transmitted by the LCT packets.

According to an embodiment of the present invention, the TOI field may be divided into at least three regions, a first region of the at least three regions may include fragment type information for identifying a type of signaling fragment including the signaling instance, a second region of the at least three regions may include fragment type extension information for identifying a lower type of a type of signaling fragment identified by the fragment type information, and a third region of the at least three regions may include the fragment type information and version information indicating a version of an object identified by the fragment type extension information.

According to an embodiment of the present invention, the fragment type information may identify whether the signaling fragment corresponds to USBD/USD fragment, S-TSID fragment, or MPD fragment.

According to an embodiment of the present invention, the fragment type information, the fragment type extension information, and the version information may be used to filter the signaling fragment by the receiver.

FIG. 142 is a diagram illustrating a broadcast system according to an embodiment of the present invention.

According to an embodiment of the present invention, the broadcast system may include a transmitter J142100 and/or a receiver J142200.

The transmitter J142100 may include a data encoder J142110, a signaling encoder J142120, a processor J142130, and a broadcast signal generator J142140.

The data encoder J142110 may generate broadcast data for one or more broadcast services.

The signaling encoder J142120 may generate first level signaling information including information for describing attribute of one or more broadcast services and generate second level signaling information including information for listing one or more broadcast services. The signaling encoder J142120 may include signaling for generating one or more signaling layer.

The processor J142130 may generate link layer packets including the encoded broadcast data, the first level signaling information, and the second level signaling information.

The broadcast signal generator J142140 may generate a broadcast signal including the generated link layer packets.

Here, the signaling encoder J142120 may generate signaling instance included in the first level signaling information, generate signaling template for the first level signaling information, generate Diff data including data on a difference between the generated signaling instance and the generated signaling template, and generate first level signaling information including the Diff data.

The receiver J142200 may include a signal receiver J142210, a processor J142220, and/or a display J142230.

The signal receiver J142210 may receive a signal. The signal receiver J142210 may include a broadcast signal receiver for receiving a broadcast signal and/or a network interface for receiving a broadband signal.

The processor J142220 may process a series of data in the receiver. The processor J142220 may process data according to each protocol of each protocol described in the specification.

The display J142230 may reproduce media the processed data.

Modules or units may be processors executing consecutive processes stored in a memory (or a storage unit). The steps described in the aforementioned embodiments can be performed by hardware/processors. Modules/blocks/units described in the above embodiments can operate as hardware/processors. The methods proposed by the present invention can be executed as code. Such code can be written on a processor-readable storage medium and thus can be read by a processor provided by an apparatus.

While the embodiments have been described with reference to respective drawings for convenience, embodiments may be combined to implement a new embodiment. In addition, designing a computer-readable recording medium which stores programs for implementing the aforementioned embodiments is within the scope of the present invention.

The apparatus and method according to the present invention are not limited to the configurations and methods of the above-described embodiments and all or some of the embodiments may be selectively combined to obtain various modifications.

The methods proposed by the present invention may be implemented as processor-readable code stored in a processor-readable recording medium included in a network device. The processor-readable recording medium includes all kinds of recording media storing data readable by a processor. Examples of the processor-readable recording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device and the like, and implementation as carrier waves such as transmission over the Internet. In addition, the processor-readable recording medium may be distributed to computer systems connected through a network, stored and executed as code readable in a distributed manner.

Although the preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, without departing from the scope and spirit of the invention as disclosed in the accompanying claims. Such modifications should not be individually understood from the technical spirit or prospect of the present invention.

Both apparatus and method inventions are mentioned in this specification and descriptions of both the apparatus and method inventions may be complementarily applied to each other.

Those skilled in the art will appreciate that the present invention may be carried out in other specific ways than those set forth herein without departing from the spirit and essential characteristics of the present invention. Therefore, the scope of the invention should be determined by the appended claims and their legal equivalents, not by the above description, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.

In the specification, both the apparatus invention and the method invention are mentioned and description of both the apparatus invention and the method invention can be applied complementarily.

MODE FOR INVENTION

Various embodiments have been described in the best mode for carrying out the invention.

INDUSTRIAL APPLICABILITY

The present invention is applied to broadcast signal providing fields.

Various equivalent modifications are possible within the spirit and scope of the present invention, as those skilled in the relevant art will recognize and appreciate. Accordingly, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents. 

1-14. (canceled)
 15. A method of transmitting a broadcast signal, the method comprising: generating broadcast data for a broadcast service; generating first level signaling information including information describing attributes of the broadcast service; generating second level signaling information including information for listing one or more broadcast services; and transmitting the broadcast signal including the broadcast data, the first level signaling information and the second level signaling information, wherein the information describing attributes of the broadcast service includes first identification information to identify the broadcast service, wherein the information for listing one or more broadcast services includes third identification information to be used to link to the first level signaling information, wherein a value of the first identification information has a same value as the third identification information, wherein the generated first level signaling information is carried in at least one transport session, and wherein the second level signaling information further includes information to acquire the at least one transport session.
 16. The method of claim 15, wherein generating the first level signaling information further comprises: generating Diff data including data corresponding to a difference between the first level signaling information and a signaling template transmitted in advance to a receiver; and transmitting the Diff data.
 17. The method of claim 16, wherein the Diff data includes: signaling template identification information for identifying the signaling template to which the Diff data is applied; and signaling template version information for indicating a version of the signaling template identified by the signaling template identification information.
 18. The method of claim 15, wherein the at least one transport session includes one or more Layered Coding Transport (LCT) packets and wherein the one or more LCT packets include a Transport Object Identifier (TOI) field for identifying an object carried in the LCT packets.
 19. The method of claim 18, wherein the TOI field is split into at least three parts, wherein a first part of the at least three parts includes fragment type information for identifying a type of a fragment of the first level signaling information, wherein a second part of the at least three parts includes fragment type extension information for identifying a sub type of the type of the fragment identified by the fragment type information, and wherein a third part of the at least three parts includes version information for indicating a version of the object identified by the fragment type information and the fragment type extension information.
 20. The method of claim 19, wherein the fragment of the first level signaling information identified by the fragment type information is one of a User Service Bundle Description/User Service Description (USBD/USD) fragment, a Service-based Transport Session Instance Description (S-TSID) fragment, and a Media Presentation Description (MPD) fragment.
 21. The method of claim 19, wherein the fragment type information, the fragment type extension information and the version information are used for filtering of the first level signaling information by a receiver.
 22. The method of claim 15, wherein the second level signaling information further includes information for identifying a provider related to the one or more broadcast services.
 23. The method of claim 15, wherein the information describing attributes of the broadcast service further includes second identification information to be used to link to service guide data.
 24. An apparatus for transmitting a broadcast signal, the apparatus comprising: a data encoder for generating broadcast data for a broadcast service; a first level signaling encoder for generating first level signaling information including information describing attributes of the broadcast service; a second level signaling encoder for generating second level signaling information including information for listing one or more broadcast services; and a transmitting unit for transmitting the broadcast signal including the broadcast data, the first level signaling information and the second level signaling information, wherein the information describing attributes of the broadcast service includes first identification information to identify the broadcast service and second identification information to be used to link to service guide data, wherein the information for listing one or more broadcast services includes third identification information to be used to link to the first level signaling information, wherein a value of the first identification information has a same value as the third identification information, wherein the generated first level signaling information is carried in at least one transport session, and wherein the second level signaling information further includes information to acquire the at least one transport session.
 25. The apparatus of claim 24, wherein the first level signaling encoder further generates Diff data including data corresponding to a difference between the first level signaling information and a signaling template transmitted in advance to a receiver and transmits the Diff data.
 26. The apparatus of claim 25, wherein the Diff data includes: signaling template identification information for identifying the signaling template to which the Diff data is applied; and signaling template version information for indicating a version of the signaling template identified by the signaling template identification information.
 27. The apparatus of claim 24, wherein the at least one transport session includes one or more Layered Coding Transport (LCT) packets and wherein the one or more LCT packets include a Transport Object Identifier (TOI) field for identifying an object carried in the LCT packets.
 28. The apparatus of claim 27, wherein the TOI field is split into at least three parts, wherein a first part of the at least three parts includes fragment type information for identifying a type of a fragment of the first level signaling information, wherein a second part of the at least three parts includes fragment type extension information for identifying a sub type of the type of the fragment identified by the fragment type information, and wherein a third part of the at least three parts includes version information for indicating a version of the object identified by the fragment type information and the fragment type extension information.
 29. The apparatus of claim 28, wherein the fragment of the first level signaling information identified by the fragment type information is one of a User Service Bundle Description/User Service Description (USBD/USD) fragment, a Service-based Transport Session Instance Description (S-TSID) fragment, and a Media Presentation Description (MPD) fragment.
 30. The apparatus of claim 28, wherein the fragment type information, the fragment type extension information and the version information are used for filtering of the first level signaling information by a receiver.
 31. The apparatus of claim 24, wherein the second level signaling information further includes information for identifying a provider related to the one or more broadcast services.
 32. The apparatus of claim 24, wherein the information describing attributes of the broadcast service further includes second identification information to be used to link to service guide data. 